In my opinion, the documentation should stay with the code in the same repository. Otherwise you would need to manage the documentation source manually, for example when you backport a feature from version B to A. With a single repository, you just check out that version and re-build the documentation.
You should look at SQLAlchemy project, they have multiple versions of their documentation available on the same site. The documentation is in the same repository and they copy the output of each version into their static homepage folders.
发布评论
评论（1）
在我看来，文档应该与代码放在同一个存储库中。否则，您将需要手动管理文档源，例如，当您将功能从版本 B 反向移植到 A 时。使用单个存储库，您只需签出该版本并重新构建文档。
您应该查看 SQLAlchemy 项目，他们在同一站点上提供了多个版本的文档。该文档位于同一存储库中，并且它们复制输出< /a> 将每个版本放入其静态主页文件夹中。
In my opinion, the documentation should stay with the code in the same repository. Otherwise you would need to manage the documentation source manually, for example when you backport a feature from version B to A. With a single repository, you just check out that version and re-build the documentation.
You should look at SQLAlchemy project, they have multiple versions of their documentation available on the same site. The documentation is in the same repository and they copy the output of each version into their static homepage folders.