Skip to content

Latest commit

 

History

History
37 lines (27 loc) · 1.56 KB

README.md

File metadata and controls

37 lines (27 loc) · 1.56 KB

Documentation

Add/Modify Content

Create a *.md file or *.rst file in this /docs directory, and they will be added as new pages automatically.

The API reference page, api.rst uses sphinx.ext.autodoc to automatically pull docstrings from GroClient and CropModel, so any function docstrings added or modified in those modules will be updated in the documentation. All other pages are manually written.

Build docs locally

  • Install Poetry (see CONTRIBUTING.md).
  • poetry install -E docs to install extra dependencies.
  • rm -r docs/_build/html && poetry run sphinx-build -W --keep-going docs docs/_build/html to build the docs for your current branch.

This should generate html output in api-client/docs/_build/html that you can open up and view in a web browser.

Automatic builds

Every time continuous integration runs, it re-builds the documentation for any currently-open branches and pushes the result to the gh-pages branch (even for unmerged pull requests). If you edit any documentation pages or docstrings, navigate to your feature branch's documentation and verify that the changes are as intended.

Branches aren't listed in the version-selector widget (since we don't want to show them to external users). You have to edit the URL manually: https://developers.gro-intelligence.com/<YOUR-BRANCH-NAME-HERE>/index.html

If anything in continuous integration fails, the documentation building step is skipped. CI calls bin/sphinx_push_ghpages.sh to build and push the docs.