[petsc-dev] plan to transition to new documentation and webpages?

Barry Smith bsmith at petsc.dev
Sat Mar 6 15:22:45 CST 2021


   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 it ourselves we have much more flexibility since you ware not restricted to running only a Sphinx document builder script.

   Patrick, Jacob and others have done a fantastic job moving a lot of material into much better pages, it seems nuts not to be using it all.

  Barry


> On Mar 6, 2021, at 12:33 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> 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
>> 
>> 
> 



More information about the petsc-dev mailing list