Documentation Quickstart#
We have recently converted our documentation to use Jupyter Book, which plays nicely with our documentation hosting service Read the Docs. A key motivation in doing so is to enable first class support for executable code cells and even full Jupyter notebooks!
Jupyter Book uses MyST (Markedley Structured Text) Markdown (see their overview for details). MyST supports many of the same reStructuredText directives already in use within PDAL’s documentation, though the look and feel of the raw docs will certainly have more of Markdown feel to them.
Rather than provide our own Jupyter Book and MyST markdown overview, we’ll encourage developers to visit the respective projects to learn more. And be sure to browse our new docs to familiarize yourself with how we have adopted it.
Some key points to remember when writing documentation.
Start by creating a new
.md
file within thedoc
folder and populating it with your desired content.Next (or first, it doesn’t really matter!), take a look at
_toc.yml
and add a reference to your new file where you would like it to appear within the rendered docs. More on the TOC and structure of Jupyter Books here.If your documentation has any references cited, be sure to add the corresponding BibTex entry to
references.bib
at the root of thedoc
folder.If you have added executable content to your docs and it requires a new package, please add it to
environment.yml
at the root of thedoc
folder so that Read the Docs will be able to properly setup the environment.Documentation is automatically built for each GitHub Pull Request commit. You can always preview the rendered documentation by following the links in the pull request.
Documentation can be built locally as well using the Jupyter Book CLI. I’m currently using the following Mamba environment to setup my environment. Once your environment is setup and
jupyter-book
is installed, you should be able to simply runjb build doc
.name: jb-build-pdal-docs channels: - conda-forge dependencies: - python-pdal - jupyter-book - ca-certificates - certifi - openssl - sphinx-notfound-page - sphinxcontrib-jquery - sphinxcontrib-bibtex