Hi, I'd like to follow-up the old thread: How to manage many versions?
http://groups.google.com/group/sphinx-dev/browse_thread/thread/fb8ba5cfa890b587/ I maintain a small library project written in C++. I'd like to use Sphinx to maintain the library website + user documentation per release version. I have found similar thread How to manage many versions? http://groups.google.com/group/sphinx-dev/browse_thread/thread/fb8ba5cfa890b587/ I think of basic structure like this: mylib/ <- website root mylib/... mylib/tutorial/... mylib/doc <- list of documentation per release version mylib/doc/1.0.0 mylib/doc/2.0.0 ... I'm trying to figure out best practical configuration for this structure. I have root configuration mylib/conf.py where I control the website structure and content. I could put .rst files into mylib/doc/1.0.0 and mylib/doc/2.0.0 build them using the root conf.py But then it seems tricky to control toctree for website and for docs. So, I think it may be more practical to separate website config/build from per release documentation config/builds: mylib/conf.py mylib/doc/1.0.0/conf.py mylib/doc/2.0.0/conf.py but all these will use the same layout template, so I can have consistent look, e.g. links in page header, etc.. This way I can easily achieve consistent toctree per documentation release. It should be easy to walk the directories and perform builds for website and for each doc version separately. Does this approach sound? Any better alternative? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org -- 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.
