project-documentation
Documentation pipeline for embedded projects — CI-friendly, framework-agnostic.
project-documentation is a GitHub composite action and Python package that covers the full documentation lifecycle for embedded software projects:
- Validate requirements — check YAML requirement files against a JSON schema
- Validate documents — enforce frontmatter fields and required sections in Markdown architecture/design/theory documents
- Generate requirements PDF — render YAML requirements to a versioned PDF via a Markdown template
- Build documentation PDFs — convert Markdown documentation directories and YAML requirements to PDFs using Pandoc
- Traceability matrix — map requirements to Gherkin scenarios (with optional JUnit pass/fail status), output Markdown and optionally PDF
✨ Features
| Capability | Description |
|---|---|
| Requirements validation | JSON schema validation for YAML requirement files |
| Document validation | Frontmatter fields, required H2 sections, no code blocks in design docs |
| Requirements PDF | Template-driven PDF from YAML requirements |
| Documentation PDFs | Per-directory Markdown → PDF + combined requirements PDF |
| Traceability matrix | Requirements ↔ scenarios mapping with coverage statistics |
| PR comment | Idempotent PR comments (traceability matrix) |
| GitHub Action | Composite action with feature flags for each capability |
🚀 Quickstart
1. Install
pip install project-documentation
2. Use in GitHub Actions
- uses: embedded-pro/project-documentation@v0
with:
run-validate-requirements: 'true'
run-validate-documents: 'true'
run-generate-requirements-pdf: 'true'
run-build-documentation-pdfs: 'true'
run-traceability-matrix: 'true'
version: ${{ github.ref_name }}
See docs/usage.md for the full input/output reference.
3. Run from the command line
# Validate requirements against a JSON schema
project-documentation-validate-requirements \
--schema documentation/tools/requirement.schema.json \
--requirements-dir documentation/requirements
# Validate Markdown documentation
project-documentation-validate-documents \
--documents-dir documentation \
--doc-type architecture
# Generate requirements PDF
project-documentation-generate-requirements-pdf \
--requirements-dir documentation/requirements \
--template documentation/templates/requirements.md \
--output documentation/output/requirements.pdf
# Build all documentation PDFs
project-documentation-build-pdfs \
--version v1.2.3 \
--output-dir docs-pdf \
--docs-dirs documentation/architecture documentation/design documentation/theory \
--requirements-dir documentation/requirements
# Generate traceability matrix
project-documentation-traceability-matrix \
--requirements-dir documentation/requirements \
--features-dir integration_tests/software_in_the_loop/features \
--output docs-pdf/traceability-matrix.md \
--junit-xml sil-test-report.xml
📚 Documentation
| File | Contents |
|---|---|
| docs/usage.md | CLI flags, action inputs/outputs, examples |
| CONTRIBUTING.md | Dev setup, testing, release process |
| CHANGELOG.md | Version history |
⚠️ System dependencies
The PDF-generating capabilities require:
pandoc— document converterpdflatex(viatexlive-latex-recommended,texlive-latex-extra,texlive-fonts-recommended)
The GitHub Action installs these automatically when any PDF feature flag is enabled.
📄 License
Apache-2.0 — see LICENSE.
Metadata
Release files for project-documentation 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 | Provenance | Actions |
|---|---|---|---|---|
| project_documentation-0.2.0.tar.gz | 18.9 kB | With provenance | Details for project_documentation-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| project_documentation-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for project_documentation-0.2.0-py3-none-any.whl |
Total release size: 34.0 kB
Release files / project_documentation-0.2.0.tar.gz
| Download URL | project_documentation-0.2.0.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f0c2e7816621b873ded4549789d6fb12f688ad98fa5922804a36d037344d97a
|
|
BLAKE2b-256 checksum How to use checksums |
6f7608e672896318de8cf4389bf07425896b86c6da42c3131ad8810f5a9456dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 24, 2026.
Transparency logRelease files / project_documentation-0.2.0-py3-none-any.whl
| Download URL | project_documentation-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f7210b01ae0347ec1aceab36ff7bb2f364e72d4fa83edb8d3aa83ec9f3a7f29
|
|
BLAKE2b-256 checksum How to use checksums |
52d40af96beef3af41f55c731119575b2e4f7e0e64c117ab05b5a8a89cac6d0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 24, 2026.
Transparency logSecurity for project-documentation 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for project_documentation-0.2.0.tar.gz
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 May 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.