TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Retiring the AWS Documentation on GitHub

5 点作者 jeffbarr将近 2 年前

2 条评论

myroon5将近 2 年前
(copying from <a href="https:&#x2F;&#x2F;old.reddit.com&#x2F;r&#x2F;aws&#x2F;comments&#x2F;13ki1o9&#x2F;retiring_the_aws_documentation_on_github&#x2F;" rel="nofollow">https:&#x2F;&#x2F;old.reddit.com&#x2F;r&#x2F;aws&#x2F;comments&#x2F;13ki1o9&#x2F;retiring_the_a...</a>)<p>Ecstatic this is finally being publicly addressed after half a decade<p>The actual <i>awsdocs</i> source code was never really open. The internal source code <i>wasn&#x27;t even the same language</i> and the Github markdown files were just build artifacts generated from the internal source code using something like XSLT. Some services didn&#x27;t upload anything at all for years<p>Public issues will be sorely missed if repos are archived, but soliciting pull requests in the initial announcement never made complete sense because PRs usually created more work for AWS&#x27; tech writers because PRs edited build artifacts instead of the actual source code used to generate them<p>---<p>Was never a tech writer myself, but always empathized with them knowing how much AWS leaders rush launches out before they&#x27;re ready and refuse to make necessary investments post-launch while individual contributors slog through maintaining hacks like this for half a decade before leaders publicly acknowledge the extent of internal issues
scrum-treats将近 2 年前
It&#x27;s weird that there&#x27;s no way to export to markdown, and sync internal docs with Github in an automated fashion. At any rate, glad the code samples and templates will remain.