Distribution Statement
Documentation Builder#
We use Sphinx
, pinkrst
and brassy
to build our documentation.
For more information on how to use the documentation builder,
see Documentation Building.
Mechanism#
The build script does the following actions in the following order:
Validates the provided
repo_path
exists and is a git directoryVerifies the provided
package_name
is installedCopies build files to a temporary build directory that is deleted after the program exits
Copies non-documentation files (eg.
CODE_OF_CONDUCT.md
) into a specialimport
directory at the top of the docs directory for access during buildingIf building documentation for a plugin (aka
package_name
is notgeoips
), it copies static files from the GeoIPS documentation directory that are needed for buildingGenerates a top level
index.rst
fromindex.template.rst
and replaces placeholder strings with actual section paths or removes them depending if those sections are present in the documentation.Builds release notes with brassy from sub-directories of the
releases
directory (any sub-directory namedupcoming
is skipped as a special case for the release process)A release index file is generated that indexes the newly generated and old
.rst
files inreleases/
Sphinx’s
apidoc
tool is used to generate.rst
files for the packages Python modulesSphinx is used to build html files from the generated
.rst
filesIf everything succeeds, the built html files are copied to the specified output directory