Awesome, thanks for look at this.
Barry > On Mar 7, 2021, at 1:37 AM, Patrick Sanan <[email protected]> wrote: > > 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 with local > links (and their internal relative links work). Hopefully I can have a demo > in the next couple of days. > >> Am 06.03.2021 um 19:33 schrieb Satish Balay via petsc-dev >> <[email protected]>: >> >> 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 plan to transition to the new documentation and webpages? >>> >>> I go to https://www.mcs.anl.gov/petsc/index.html >>> <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff >>> etc. Our next release is coming up soon and it would be nice to have >>> transitioned out of the old material and to the new material by/at the new >>> release. >>> >>> What do we need to do to make this happen? >>> >>> Thanks >>> >>> Barry >>> >>> >> >
