About 5 many years in the past I announced that AWS Documentation is Now Open up Resource and on GitHub. Soon after a prolonged period of time of experimentation we will archive most of the repos starting up the week of June 5th, and will devote all of our assets to instantly strengthening the AWS documentation and web page.
The key supply for most of the AWS documentation is on inside devices that we experienced to manually sync with the GitHub repos. Inspite of the finest efforts of our documentation crew, preserving the general public repos in sync with our inner kinds has proven to be incredibly difficult and time consuming, with several guide ways and some parallel modifying. With 262 individual repos and thousands of aspect launches each year, the overhead was quite higher and really consumed treasured time that could have been place to use in ways that much more right enhanced the high-quality of the documentation.
Our intent was to raise worth to our consumers by means of openness and collaboration, but we learned as a result of purchaser feed-back that this wasn’t always the scenario. Following very carefully considering numerous possibilities we made the decision to retire the repos and to invest all of our resources in earning the articles improved.
Repos made up of code samples, sample applications, CloudFormation templates, configuration data files, and other supplementary sources will remain as-is given that all those repos are main sources and get a large amount of engagement.
To help us strengthen the documentation, we’re also concentrating extra sources on your opinions:
We check out the thumbs-up and thumbs-down metrics on a weekly basis, and use the metrics as leading-amount tips to locations of the documentation that could be enhanced. The incoming responses creates tickets that are routed directly to the person or the team that is liable for the web page. I strongly motivate you to make recurrent use of equally feedback mechanisms.