Currently, the PAL documentation is built using reStructuredText, and built using Sphinx.
Installing this on Windows requires jumping through a few hoops, although I am aware it is possible to install Sphinx on the Windows Subsystem for Linux if necessary.
What I am looking for, is feedback from some other developers on whether not we should stick with Sphinx, or change to using another methodology.
Some options include switching to markdown, and using existing conversion tools to convert to html, or converting directly to html.
Some benefits of remaining with Sphinx includes the ability to have search which works within the offline documentation.
Note that regardless of the method chosen, the documentation will be updated to maintain consistent branding, i.e. header/footer will be similar/identical to the main site or alternately to generic help files.