Documentation automation pipeline
With Astro Starlight powering IssueSuite docs, we enforce the same Frontier gates used across the CLI. This guide explains how to run doc builds locally and in CI.
Local workflow
Section titled “Local workflow”cd docs/starlightnpm installnpm run checknpm run build
The check
script executes astro check --flags minimal
to lint Markdown, validate frontmatter, and ensure links stay healthy.
Nox session
Section titled “Nox session”Run nox -s docs
to install dependencies (cached per session) and perform npm run check && npm run build
. The session exits non-zero if either step fails, keeping documentation within release readiness criteria.
CI integration
Section titled “CI integration”Add a job to your workflow:
jobs: docs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - uses: actions/setup-node@v4 with: node-version: "20" cache: "npm" cache-dependency-path: docs/starlight/package-lock.json - name: Install dependencies run: npm install working-directory: docs/starlight - name: Build documentation run: npm run build working-directory: docs/starlight
Quality expectations
Section titled “Quality expectations”- Every page includes
title
,description
, and Diátaxis category metadata. - Tests in
tests/test_documentation_structure.py
guard against missing frontmatter and unsynchronised ADR entries. Next Steps.md
tracks documentation milestones so we continuously evolve governance.