如果能有更多这样的风格就好了。它对于 wiki 来说非常有效，因为社区可以更改内容。我发现 gem 文档有时会出现错误。我认为让文档可编辑会很好，因为人们可以重写不清楚的部分，使其更加用户友好
很好的建议！
Would be nice if it were more of a style like that. It's worked well for wiki's having the content changeable by the community. I've found that gem documentation can be hit or miss sometimes. I think having the documentation editable would be good because people could rewrite parts that are unclear making it much more user friendly
This kind of documentation (tutorial, non-generated doc, ...) is better addressed by a wiki.
Most of the public source container out there now integrates one in their features. GitHub recently improves its own wiki system. It also proposes GitHub pages (for publishing content to the web by simply pushing content to one of your GitHub hosted repositories, with user pages or project pages, and with Jekyll for even more Makdown file formats)
发布评论
评论（2）
如果能有更多这样的风格就好了。它对于 wiki 来说非常有效，因为社区可以更改内容。我发现 gem 文档有时会出现错误。我认为让文档可编辑会很好，因为人们可以重写不清楚的部分，使其更加用户友好
很好的建议！
Would be nice if it were more of a style like that. It's worked well for wiki's having the content changeable by the community. I've found that gem documentation can be hit or miss sometimes. I think having the documentation editable would be good because people could rewrite parts that are unclear making it much more user friendly
Great suggestion!
这种类型的文档（教程、非生成的文档……）最好通过 wiki 来处理。
现在大多数公共源代码容器都在其功能中集成了一项功能。
GitHub 最近改进了其自己的 wiki 系统。
它还建议 GitHub 页面（只需将内容推送到 GitHub 托管存储库之一即可将内容发布到网络） ，使用用户页面或项目页面，以及使用 Jekyll 了解更多Makdown 文件格式）
This kind of documentation (tutorial, non-generated doc, ...) is better addressed by a wiki.
Most of the public source container out there now integrates one in their features.
GitHub recently improves its own wiki system.
It also proposes GitHub pages (for publishing content to the web by simply pushing content to one of your GitHub hosted repositories, with user pages or project pages, and with Jekyll for even more Makdown file formats)