Writing documentation¶
Documentation comes in two parts: docstrings and user-guide documentation.
Docstrings – written at the start of a function and give essential information about how it should be used, such as which arguments can be passed to it and what the syntax should be. The docstrings need to follow the numpy specification, as shown in this example.
User-guide documentation – A description of the functionality of the code and how to use it with examples and links to the relevant code.
When writing both the docstrings and user guide documentation, it is useful to have some kind of data which the users can use themselves. Artificial datasets for this purpose can be found in hyperspy.datasets.artificial_data.
Build the documentation – To check the output of what you wrote, you can build
the documentation by running the make
command in the hyperspy/doc
directory. For example make html
will build the whole documentation in
html format. See the make command documentation for more details.
To install the documentation dependencies, run either
$ conda install hyperspy-dev
or
$ pip install hyperspy[build-doc]
When writing documentation the Python package sphobjinv can be useful for writing cross-references. For example, to find how to write a cross-reference to :py:method:`hyperspy.signal.BaseSignal.set_signal_type`:
$ sphobjinv suggest doc/_build/html/objects.inv set_signal_type -st 90
Name Score
--------------------------------------------------------- -------
:py:method:`hyperspy.signal.BaseSignal.set_signal_type` 90