-
Notifications
You must be signed in to change notification settings - Fork 39
Change log
For the full change log, see the commits or pull requests. This change log lists big and relevant changes that every user of the starter pack should be aware of and that might require an action.
Added some common terms to the custom wordlist, including Canonical-specific terms.
Unpinned the Sphinx version again since the issues (mentioned below, 2023/08/21) are now fixed.
Switched the GitHub documentation checks to use a reusable workflow.
Pinned the Sphinx version to prevent some current bugs (that will hopefully be resolved soon):
- The notfound extension isn't compatible with the latest Sphinx version 7.2.2: https://github.com/readthedocs/sphinx-notfound-page/issues/219
- When requiring a Sphinx version <7.2.2, RTD automatically uses 6.2.1, which is not compatible with the current Furo version: https://github.com/pradyunsg/furo/discussions/693
Therefore, we currently pin the Sphinx version to 7.1.2.
Added a GitHub bot that can be used to sync issues from GitHub to Jira. See (Optional) Synchronise GitHub issues to Jira for instructions on how to set it up.
Summary of relevant changes for the last month:
-
Moved the content files that were meant to show how to set up Diataxis documentation to a separate repository: https://github.com/canonical/example-product-documentation
This leaves only the files that cover configuration and styling in the starter pack, which should make it easier to keep documentation sets in sync with the starter pack.
-
Added a header to the documentation to integrate the documentation (hosted on readthedocs) with the product website. The header can be customised with the product name and logo, and you can add custom links to the "More resources" section.
See https://github.com/canonical/sphinx-docs-starter-pack#configure-the-header
-
Split the configuration file into a common
conf.py
file and a customcustom_conf.py
file. All project-specific configuration should go into thecustom_conf.py
file, while theconf.py
file should not be touched. This should make it easier to keep the configuration in sync with the starter pack.