spiri-docs
Sphinx extension for Spiri controlled documents — operational manuals and anything else with a revision number that someone outside the company relies on.
# docs/conf.py
extensions = ["myst_parser", "spiri_docs"]
Everything follows from a revisions.yaml beside docs/:
document_number: SPIRI-OM-001
regulator_facing: true
distribution_statement: Uncontrolled when printed.
revisions:
- revision: "1.0"
date: 2026-07-19
effective_date: 2026-08-01
author: A. Author
approver: B. Approver
summary: Initial issue.
On every build the extension:
- validates the file — a
regulator_facingdocument without aneffective_dateorapproverfails the build rather than shipping; - sets
versionandreleaseto the current revision; - exposes
{{ document_number }},{{ revision }},{{ effective_date }},{{ approver }}and friends as MyST substitutions for the cover page; - stamps document number, revision and
Page N of Minto the PDF footer; - names the PDF
SPIRI-OM-001_rev1.0.pdf.
And provides one directive:
```{revision-history}
which renders the history newest-first, showing only the columns the document
actually populates.
## Why an extension and not the template
`spiri-doc-template` runs once, at project generation. This runs on every build.
Validation, revision plumbing, and PDF document control have to hold every time
the docs are built — a template can only put a correct file down on day one and
has no way to detect drift afterwards. Theme, CSS and structure stay in the
template, where being decided once is the point.
## Configuration
| Option | Default | Meaning |
| --- | --- | --- |
| `spiri_docs_revisions` | `"../revisions.yaml"` | Path to the revision file, relative to `conf.py`. |
## Not here yet
Hazard admonitions (DANGER / WARNING / CAUTION / NOTICE). Which standard to
follow — ANSI Z535.6, ISO 3864 — is an editorial decision, and shipping markup
before it is made means migrating every manual later. Sphinx's built-in
`danger`, `warning`, `caution` and `note` are fine in the meantime.
Metadata
Release files for spiri-docs 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| spiri_docs-0.2.0.tar.gz | 58.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spiri_docs-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 87.5 kB
Release files / spiri_docs-0.2.0.tar.gz
| Download URL | spiri_docs-0.2.0.tar.gz |
|---|---|
| Size | 58.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b67cb2e180a3dc07e76aa11dcbc3ea30a087038adad38b268565b02ee5c14b42
|
|
BLAKE2b-256 checksum How to use checksums |
57daaf7738b00bfb8df212fb278df360fbd5df3b69a5734c247751db44856840
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 20, 2026.
Transparency logRelease files / spiri_docs-0.2.0-py3-none-any.whl
| Download URL | spiri_docs-0.2.0-py3-none-any.whl |
|---|---|
| Size | 29.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec524e2574981120753fd9861b1170c1a561ed1857bdc6248309857fb3ffbc90
|
|
BLAKE2b-256 checksum How to use checksums |
91d0c3752bd2eda6d4d2dae6a900221a9c9de6652b1e955e71de8180861704ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 20, 2026.
Transparency log