Documentation Guide
The documentation is built using mkdocs. We use mkdocstrings and mkdocs-autoapi to automatically generate the API references.
Installing Dependencies
To install the documentation dependencies:
Building the Docs
To preview the documentation locally:
To build the documentation:
Navigation
The navigation is handled in mkdocs.yml:
nav:
- Overview: index.md
- User Guide:
- Configuration & Templates Overview: user/overview.md
- Building Configuration: user/configuration.md
- Building Templates: user/templates.md
- Simple Example - WAVI: user/WAVI_example.md
- Developer Guide:
- Contribution:
- Contributing: developer/contribution/contributing.md
- Software Guide: developer/contribution/software.md
- Documentation Guide: developer/contribution/documentation.md
- Code of Conduct: developer/contribution/code_of_conduct.md
- Functionality:
- Technical Overview: developer/functionality/technical.md
- Testimonials: testimonials.md
- Change Log: change_log.md
- Acknowledgements: acknowledgements.md
- LICENSE: license.md
Note that the API section (which is not listed under nav:) is automatically generated using mkdocstrings and mkdocs-autoapi, when you call mkdocs serve.
This is because we use the following configuration in mkdocs.yml:
plugins:
- search
- mkdocs-autoapi:
autoapi_add_nav_entry: API
- mkdocstrings:
handlers:
python:
paths:
- .
options:
show_submodules: true
docstring_style: google
heading_level: 3
Therefore, there is no need to create or edit .md files when you make a change to the code under model_ensembler/. Do make sure you update the docstrings if needed.
Docstrings Style
For the docstrings, please follow the Google Style Guide. For more information on mkdocstrings, see their Docstring Options.