Retiring the AWS Documentation on GitHub


Voiced by Polly

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 a lot of the repos beginning the week of June fifth, and can dedicate all of our sources to instantly bettering the AWS documentation and web site.

The first supply for a lot of the AWS documentation is on inner techniques that we needed to manually sync with the GitHub repos. Regardless of the very best efforts of our documentation staff, holding the general public repos in sync with our inner ones has confirmed to be very tough and time consuming, with a number of handbook steps and a few parallel modifying. With 262 separate repos and hundreds of characteristic launches yearly, the overhead was very excessive and truly consumed valuable time that would have been put to make use of in ways in which extra instantly improved the standard of the documentation.

Our intent was to extend worth to our clients by way of openness and collaboration, however we discovered by way of buyer suggestions that this wasn’t essentially the case. After fastidiously contemplating many choices we determined to retire the repos and to speculate all of our sources in making the content material higher.

Repos containing code samples, pattern apps, CloudFormation templates, configuration information, and different supplementary sources will stay as-is since these repos are major sources and get a excessive degree of engagement.

To assist us enhance the documentation, we’re additionally focusing extra sources 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 might be improved. The incoming suggestions creates tickets which can be routed on to the particular person or the staff that’s liable for the web page. I strongly encourage you to make frequent use of each suggestions mechanisms.

Jeff;



Leave a Reply

Your email address will not be published. Required fields are marked *