register-referentie

eho/register-referentie

Fork 0

Author	SHA1	Message	Date
not	b444e0c680	ci(docs): build the MkDocs site with --strict in CI (refs #173 ) (#189 ) CI / verify-stack (push) Blocked by required conditions Details Deploy to Talos / deploy (push) Waiting to run Details CI / k8s (push) Successful in 10s Details CI / build (push) Successful in 1m22s Details CI / lint (push) Successful in 2m5s Details CI / docs (push) Successful in 1m1s Details CI / frontend (push) In progress Details CI / unit (push) Successful in 1m29s Details CI / mutation (push) In progress Details refs #173. This is the minimum step from the issue: the site is now built in CI, not published. Publishing still needs an ADR (Gitea has no built-in Pages) or a CLAUDE.md §12 correction, so the issue stays open. - `make docs`: creates a throwaway `.venv-docs`, installs pinned `mkdocs==1.6.1` and `mkdocs-material==9.7.7`, then runs `mkdocs build --strict`. The target is also added to `make ci`. - New `docs` job in `ci.yaml` (`setup-python@v5`, then `make docs`). - Red, then green: the first commit fails on a link from `runbooks/ci.md` to a file outside `docs/`; the second turns that link into plain code. Dependency (§13): mkdocs and mkdocs-material were already the site's declared toolchain (`mkdocs.yml`) but were never installed anywhere. They give a strict link/nav/theme check. Replacing them means writing our own Markdown link checker, and `check-docs-nav.py` already covers only the nav half. Risk: Material warns that MkDocs 2.0 drops its plugin/theme system, so both are pinned exactly. No ADR, since this adds no new decision beyond what `mkdocs.yml` already assumes. Verified locally: `make docs` → `Documentation built in 0.87 seconds`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)Reviewed-on: #189	2026-09-28 13:25:40 +00:00

Author

SHA1

Message

Date

not

b444e0c680

ci(docs): build the MkDocs site with --strict in CI (refs #173 ) (#189 )

CI / verify-stack (push) Blocked by required conditions

Details

Deploy to Talos / deploy (push) Waiting to run

Details

CI / k8s (push) Successful in 10s

Details

CI / build (push) Successful in 1m22s

Details

CI / lint (push) Successful in 2m5s

Details

CI / docs (push) Successful in 1m1s

Details

CI / frontend (push) In progress

Details

CI / unit (push) Successful in 1m29s

Details

CI / mutation (push) In progress

Details

refs #173. This is the minimum step from the issue: the site is now **built** in CI, not **published**. Publishing still needs an ADR (Gitea has no built-in Pages) or a CLAUDE.md §12 correction, so the issue stays open.

- `make docs`: creates a throwaway `.venv-docs`, installs pinned `mkdocs==1.6.1` and `mkdocs-material==9.7.7`, then runs `mkdocs build --strict`. The target is also added to `make ci`.
- New `docs` job in `ci.yaml` (`setup-python@v5`, then `make docs`).
- Red, then green: the first commit fails on a link from `runbooks/ci.md` to a file outside `docs/`; the second turns that link into plain code.

**Dependency (§13):** mkdocs and mkdocs-material were already the site's declared toolchain (`mkdocs.yml`) but were never installed anywhere. They give a strict link/nav/theme check. Replacing them means writing our own Markdown link checker, and `check-docs-nav.py` already covers only the nav half. Risk: Material warns that MkDocs 2.0 drops its plugin/theme system, so both are pinned exactly. No ADR, since this adds no new decision beyond what `mkdocs.yml` already assumes.

Verified locally: `make docs` → `Documentation built in 0.87 seconds`.

🤖 Generated with [Claude Code](https://claude.com/claude-code)Reviewed-on: #189

2026-09-28 13:25:40 +00:00

Compare commits

Diff Content Not Available