User-level documentation workflow

What you need to know

We use Sphinx to generate documentation and Read the Docs to publish it. Sphinx uses reStructuredText as the base format for the documentation. To learn more about the syntax, check out this quick reference.

The NEST Simulator documentation lives alongside its code. It is contained in the doc/htmldoc directory within the NEST source code repository on GitHub.

We work with GitHub as a web-based hosting service for Git. Git allows us to keep our versions under control, with each release of NEST having its own documentation.

This workflow aims for the concept of user-correctable documentation.

Alternative text

Note

This workflow shows you how to create user-level documentation for NEST. For the developer documentation, please refer to our Developer documentation workflow.

Changing the documentation

If you notice any errors or weaknesses in the documentation, please submit an Issue in our GitHub repository.

You can also make changes directly to your forked copy of the NEST source code repository and create a pull request. Just follow the workflow below!

Setting up your environment

We recommend that you set up a full NEST developer environment using Conda (for details on Conda, see Tips for installing NEST with conda):

cd <nest_source_dir>/
conda env create -p conda/
conda activate conda/

If you later on want to deactivate or delete the build environment:

conda deactivate
rm -rf conda/

If you want to install only a minimal set of packages for building the documentation and avoid using Conda, you can use pip:

pip3 install -r <nest_source_dir>/doc/requirements.txt

If you use pip, install pandoc from your platform’s package manager (e.g. apt):

sudo apt-get install pandoc

Generating documentation with Sphinx

Now that you activated your environment, you can generate HTML files using Sphinx.

Rendering HTML

You can build and preview the documentation locally by running the following commands.

  1. Go to the build directory of NEST:

cd nest-simulator-x.y.z-build

  1. Add -Dwith-userdoc=ON to your regular CMake command:

cmake -Dwith-userdoc=ON

  1. Build the docs:

make docs

  1. Preview files. They are located in doc/htmldoc/_build/html

browser doc/htmldoc/_build/html/index.html

Note

If you are planning to install NEST, make docs is included in make install as long as you toggle on the userdoc or devdoc

After installation the files are located in <nest_install_dir>/share/doc/nest/html/index.html

Editing and creating pages

To edit existing reStructuredText files or to create new ones, follow the steps below:

  1. You can edit and/or add .rst files in the doc/htmldoc directory using your editor of choice.

  2. If you create a new page, open index.rst in the doc/htmldoc directory and add the file name under .. toctree::. This will ensure it appears on the NEST Simulator documentation’s table of contents.

  3. If you rename or move a file, please make sure you update all the corresponding cross-references.

  4. Save your changes.

  5. Re-render documentation as described above.

Note

Please see our documentation style guide for information on how to write good documentation in the NEST style.

Proceed as follows to preview your version of the documentation on Read the Docs.

  1. Check that unwanted directories are listed in .gitignore:

_build
_static
_templates

  1. Add, commit and push your changes to GitHub.

  2. Go to Read the Docs. Sign up for an account if you don’t have one.

  3. Import the project.

  4. Enter the details of your project in the repo field and hit Create.

  5. Build your documentation.

This allows you to preview your work on your Read the Docs account. In order to see the changes on the official NEST Simulator documentation, please submit a pull request.

Creating pull request

Once your documentation work is finished, you can create a pull request to the master branch of the NEST Source Code Repository. Your pull request will be reviewed by the NEST Documentation Team!