Contributing to the documentation#
Your contributions are welcome! There are many ways to contribute to the documentation:
Identify and correct typos.
Improve the description of
PyDAP
and overall the DAP model.Cookbooks! We want to know how
PyDAP
and OPeNDAP are being used, i.e. what kind of questions / problems is helping solve? what is the domains of expertise?Demostrate an optimization to access patterns, i.e. a benchmark.
An
OPeNDAP
URL! We want to learn more about available OPeNDAP data urls, and make them accessible to the broad community of PyDAP users. We are strong proponents ofdata democratization
andopen science
, and these begin by making your dataFindable
.
The documentation was built using jupyter-book, which supports different types of files. Here we use rst
and ipynb
(executable notebooks).
How to contribute to the documentation?#
To add/edit the documentation, we recommend you follow the previous guides on version control, forking, and branching. That said, you can follow the steps:
Navitate to the cloned repository
Create/activate the conda environment.
conda env create -f docs/environment.yml
conda activate pydap_docs
The docs/environment.yml
file provides a ready-to-use environment (it installs pydap-server
).
Note
If you already have mamba
installed, you can replace all conda
in the commands with mamba
.
Create a new branch, and set its upstream and use git (see steps 3 and 4 from contributing to the code)
Clean any previous built html pages with
jupyter-book clean docs --all
Build the docs by running
jupyter-book build docs
Depending on how many changes you have done to the documentation, this last step may take a while. It also depends on the type of files added to the documentation (ipynb
are slower to build).
Once the build process is finished, you can inspect the locally built html files by running:
open docs/_build/html/index.html
Note
Make sure to check that ALL notebooks were successfully built. This step is important because some of the notebooks require authentications. For testing the documentation it is OK to include passwords/tokens, but when you are getting ready to submit your PR for review, do not include these in the final version of your PR.
Push all changes and create a PR.
PyDAP
follows the recommendations of keeping thesource
files onmain
, and thebuild
files on thegh-pages
branch.
Note
Do not include passwords or tokens. You are only submitting source
files.
Once a maintaner of
PyDAP
has approved your PR it will get merged intomain
. The maintainer ofPyDAP
can publish the documentation and update thegh-pages
branch. Broadly, the steps to publish the documentation (i.e. rebuild thegh-pages
branch) are detailed and described here: https://jupyterbook.org/en/stable/start/publish.html.