[ad_1]
|
About 5 years in the past I introduced that AWS Documentation is Now Open Supply and on GitHub. After a chronic 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 assets to instantly enhancing the AWS documentation and web site.
The first supply for a lot 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 crew, retaining 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 modifying. With 262 separate repos and 1000’s of characteristic launches yearly, the overhead was very excessive and really consumed treasured time that might 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 prospects via openness and collaboration, however we realized via buyer suggestions that this wasn’t essentially the case. After rigorously contemplating many choices we determined to retire the repos and to speculate all of our assets in making the content material higher.
Repos containing code samples, pattern apps, CloudFormation templates, configuration information, 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 to areas of the documentation that might be improved. The incoming suggestions creates tickets which can be routed on to the individual or the crew that’s answerable for the web page. I strongly encourage you to make frequent use of each suggestions mechanisms.
— Jeff;
[ad_2]
Source link
