On Saturday, October 22, 2011, Mateusz Łoskot <[email protected]> wrote: > On 22 October 2011 14:26, CFK <[email protected]> wrote: >> Santoso Wijaya actually answered this quite well back in February; you >> need to use a version control system. I would suggest either git >> (http://git-scm.com/) or mercurial (http://mercurial.selenic.com/). > > I sense there is a misunderstanding. > VCS is not an issue. > My question is more related to how to organise Sphinx structure, single > conf.py file or multiple conf.py files, how to manage common and consistent > page template(s) (layout.html), etc. > >> Does that all make sense? > > It surely does, but I feel it is not of the highest relevance to my question. > Thanks anyway.
Generally the approach you tend to see is only a single docs/ and conf.py, using source control branches/tags to build the same docs for each version (using the SCS to migrate changes to documentation and keep documentation in sync with its code version). A good example of these best practices would be to wander around readthedocs.org, which is trying to be something of a best-practices host for Sphinx documentation (I am not affiliated, and don't currently use their services, but I follow their progress) including SCS-based multi-version documentation. Hope that helps, --Max Battcher -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
