Lines Matching full:documentation

6 The docgen module provides tools to generate documentation for Pigweed-based
11 documentation. Docgen provides a convenient way to combine all of the relevant
12 documentation for a project into one place, allowing downstream consumers of
14 unified source of documentation early on.
16 The documentation generation is integrated directly into the build system. Any
17 build target can depend on documentation, which allows it to be included as part
18 of a factory release build, for example. Additionally, documentation itself can
20 Any time the code is changed, documentation will be regenerated with the updated
23 Documentation overview
25 Each Pigweed module provides documentation describing its functionality, use
28 Included in a module's documentation are report cards which show an overview of
35 Pigweed documentation files are written in `reStructuredText`_ format and
41 Documentation source and asset files are placed alongside code within a module
43 groups become available for import within a special documentation generation
54 The main template for defining documentation files is ``pw_doc_group``. It is
55 used to logically group a collection of documentation source files and assets.
57 defining the module's documentation. A ``pw_doc_group`` can depend on other
62 * ``sources``: RST documentation source files.
84 documentation for a project. It depends on registered ``pw_doc_group`` targets
89 the documentation. These are added at the root level of the built documentation
97 * ``deps``: List of all ``pw_doc_group`` targets required for the documentation.
112 Generating documentation
118 using a subset of Pigweed's core documentation.
135 A documentation tree is created under the output directory. Each of the sources
155 This is the documentation tree which gets passed to Sphinx to build HTML output.
156 Imports within documentation files must be relative to this structure. In
157 practice, relative imports from within modules' documentation groups are