7.3. Contributing Docs¶
As always, please follow the basic git setup at Contributing Basics to start.
7.3.1. Edit Documentation¶
We love Docs changes!
Docs may be edited directly from a fork on Github and therefore do not require local clones! Changes can be directly installed by sending a pull request using Github in which they await approval before being added. This method is great for simple changes; however, more complex changes require more examination and thought.
7.3.2. Cross References¶
Please use Cross Reference
.. _foo: and Index tags
.. index:: at the top of pages. To reference another section, use
:ref:`[file]` to link to the proper section. This helps to build a complete, easy to navigate guide.
7.3.3. Bigger Doc Changes¶
For bigger doc changes, it is helpful to create a local environment in order to visualize the modifications. This helps make a consistent, multi-page change and enables the user to ascertain the impact of his or her changes.
The docs are automatically generated upon a successful pull request merge by the read-the-docs system. Sphinx builders generate the html and pdf docs from the files they receive. At a minimum please validate the html doc as this reduces errors and smooths integration of new content.
In order to validate the docs, a prerequisite environment is needed.
22.214.171.124. On Linux/Mac¶
Sphinx. is required to create the environment in which docs can be built.
For OS X 10.11,
pip install sphinx is sufficient to create the required environment.
With that in place,
make html will create a _build/html directory that contains the built files.
Using a browser pointed to the
file://<working_dir>/_build/html/BOOK.html should allow the verification of the changes.
An additional tip is to run
make html repeatedly in another terminal to capture changes as they are created.
while [ true ] ; do make html sleep 1 done
126.96.36.199. On Windows¶
With the environment created,
sphinx-build -b html -d _build\doctrees . _build\html will build the files. Using a browser pointed to
C://<workinf dir>/_build/html/BOOK.html should allow verification of the changes.
An additional tip is to run the builder repeatedly in a batch file or command terminal to capture changes as they are created.
cd path/to/clone :label echo building sphinx sphinx-build -b html -d _build\doctrees . _build\html timeout 1 >nul goto label
7.3.4. Documentation Expectations¶
Documentation is an integral and formal component to the development process. All documentation should be free from spelling and grammatical errors. Additionally, all documentation must adhere to a certain stylistic guide.
- All sentences must be followed by two spaces “__”, while words are separated by the standard single space “_”.
- Use primarily third person when writing documentation. First person is sometimes acceptable, but second person (you, your) is almost always not.
- Break thoughts into easy to read chunks rather than creating long paragraphs.
- Use embedded links when referencing a specific page or program.
- The oxford comma is used in the documentation.
- Lists should be bulleted. If a list item contains a term or phrase that is elaborated upon, italicize the term and set it off with a colon. See Operational Principles for an example list.