I was having the same type of question:
I have a documentation project for division x and I would like
to have the same documentation for division Y but only some files are
different.
So question is, what is the best approach to setup a correct structure
for this?
(both should have a different build html)
What I would think as a structure:
top_dir
|
|---- MakeFile
|---- build
|---------divisionx
|---------doctrees
|---------html_div_x
|---------divisiony
|---------doctrees
|---------html_div_x
|---- sources
|------ conf.py
|------ index_division_x.rst
|------ index_division_y.rst
|------ general sources
|------ all general rst files
|------ divisionXspecific
|------- Specific rst files for x
|------ divisionYspecific
|------- specific rst files for y
So goal would be to reuse the general files and add
the specific files for every division.
At the moment I dont directly see how I could do this.
An exclude based on a build parameter would be nice.
Problem now is that the conf.py is linked to one index masterfile.
Only possibility I see now is to create two different sphinx projects
for each division and symlink the general rst files but this does
not feels as the proper way to do it?
If somebody has some pointers on this would be nice
to hear your opinion on this.
On Jul 20, 12:39 pm, "Alastair Dent" <alastair.d...@imgtec.com> wrote:
> I need to be able to exclude specific rst files, depending on a built
> parameter.
>
> Is there an extension that will enable this?
--
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to sphinx-dev@googlegroups.com.
To unsubscribe from this group, send email to
sphinx-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en.
