|
About 5 years in the past I introduced that AWS Documentation is Now Open Source 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 commit all of our sources to straight enhancing the AWS documentation and web site.
The main supply for a lot of the AWS documentation is on inside methods that we needed to manually sync with the GitHub repos. Despite one of the best efforts of our documentation workforce, conserving the general public repos in sync with our inside ones has confirmed to be very tough 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 straight improved the standard of the documentation.
Our intent was to extend worth to our prospects by openness and collaboration, however we realized by buyer suggestions that this wasn’t essentially the case. After rigorously contemplating many choices we determined to retire the repos and to take a position 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 main sources and get a excessive stage 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 to areas of the documentation that may very well be improved. The incoming suggestions creates tickets which are routed on to the particular person or the workforce that’s answerable for the web page. I strongly encourage you to make frequent use of each suggestions mechanisms.
— Jeff;