|
About 5 years in the past I introduced that AWS Documentation is Now Open Supply and on GitHub. After a protracted interval of experimentation we are going to archive many of the repos beginning the week of June fifth, and can dedicate all of our assets to immediately enhancing the AWS documentation and web site.
The first supply for many of the AWS documentation is on inside methods that we needed to manually sync with the GitHub repos. Regardless of one of the best efforts of our documentation group, protecting the general public repos in sync with our inside ones has confirmed to be very troublesome and time consuming, with a number of handbook steps and a few parallel enhancing. With 262 separate repos and 1000’s of function launches yearly, the overhead was very excessive and really consumed treasured time that would have been put to make use of in ways in which extra immediately improved the standard of the documentation.
Our intent was to extend worth to our prospects via openness and collaboration, however we realized via buyer suggestions that this wasn’t essentially the case. After fastidiously contemplating many choices we determined to retire the repos and to take a position all of our assets in making the content material higher.
Repos containing code samples, pattern apps, CloudFormation templates, configuration recordsdata, and different supplementary assets will stay as-is since these repos are major sources and get a excessive stage of engagement.
To assist us enhance the documentation, we’re additionally focusing extra assets in your suggestions:
We watch the thumbs-up and thumbs-down metrics on a weekly foundation, and use the metrics as top-level tips that could areas of the documentation that could possibly be improved. The incoming suggestions creates tickets which might be routed on to the particular person or the group that’s liable for the web page. I strongly encourage you to make frequent use of each suggestions mechanisms.
— Jeff;
