I'm working on this right now - I think I have a workable way, where we just
use the "classic" docs system to build the man pages and HTML sources for each
version on RTD, and then specify those HTML files as "extra" to Sphinx, so it
just copies them over in the build and we can refer to them wi
> On Mar 6, 2021, at 4:46 PM, Jed Brown wrote:
>
> The one value-add that comes from ReadTheDocs is its version switcher, which
> we'd need to do ourselves.
>
> I've been using this strategy (for stand-alone preview) on a different
> project and it's working great. We can decide how to merg
The one value-add that comes from ReadTheDocs is its version switcher, which
we'd need to do ourselves.
I've been using this strategy (for stand-alone preview) on a different project
and it's working great. We can decide how to merge it (i.e., where the doc job
should run).
https://gitlab.com/
Is the plan still to use ReadTheDocs (which does support multiple versions
of all the docs) or to "build them ourselves"? All ReadTheDocs does is run a
Sphinx document builder script the user provides and we can do that ourselves
and don't need ReadTheDocs to do it for us. In fact, if we do
This is partly due to the complexity of having some docs from 'release' and
some from 'main' branches.
We had a way to manage this when all docs were on petsc website - but its not
clear how to do this properly with readthedocs
Satish
On Fri, 5 Mar 2021, Barry Smith wrote:
>
> What is the
