Documentation is often more important than code. This page helps you get set up on how to contribute documentation to JupyterHub.
We use sphinx to build our documentation. It takes our documentation source files (written in markdown or reStructuredText & stored under the docs/source directory) and converts it into various formats for people to read. To make sure the documentation you write or change renders correctly, it is good practice to test it locally.
docs/source
Make sure you have successfuly completed Setting up a development install.
Install the packages required to build the docs.
python3 -m pip install -r docs/requirements.txt
Build the html version of the docs. This is the most commonly used output format, so verifying it renders as you should is usually good enough.
cd docs make html
This step will display any syntax or formatting errors in the documentation, along with the filename / line number in which they occurred. Fix them, and re-run the make html command to re-render the documentation.
make html
View the rendered documentation by opening build/html/index.html in a web browser.
build/html/index.html
Tip
On macOS, you can open a file from the terminal with open <path-to-file>. On Linux, you can do the same with xdg-open <path-to-file>.
open <path-to-file>
xdg-open <path-to-file>
This section lists various conventions we use in our documentation. This is a living document that grows over time, so feel free to add to it / change it!
Our entire documentation does not yet fully conform to these conventions yet, so help in making it so would be appreciated!
pip
There are many ways to invoke a pip command, we recommend the following approach:
python3 -m pip
This invokes pip explicitly using the python3 binary that you are currently using. This is the recommended way to invoke pip in our documentation, since it is least likely to cause problems with python3 and pip being from different environments.
For more information on how to invoke pip commands, see the pip documentation.