Handbook

Maintainer — Docs release checklist

Use before publishing forge-fleet + forge-fleet-website or cutting a semver that markets doc changes.

Updated

  1. Pull & branch
  2. git pull --rebase on forge-fleet + consumer forge-fleet-website.
  3. Route / OpenAPI parity
  4. python3 scripts/check-docs-contracts.py
  5. JSON syntax
  6. python3 scripts/check-docs-json.py
  7. Internal Markdown links
  8. python3 scripts/check-docs-links.py
  9. Examples spot-check
  10. Skim docs/examples/ + docs/build-201/05-examples-and-recipes.md for stale route names.
  11. Handbook build
  12. From forge-fleet-website: python3 generator/build-site.py
  13. Confirm page count stable; delete stale website/*.html if generator leaves orphans.
  14. SEO / Hosting smoke (post-deploy)
  15. Load https://fleet.forgesdlc.com/index.html + random Learn/Begin page, confirm canonical tag present.
  16. UX smoke (static build)
  17. From forge-fleet-website: python3 scripts/check-site-smoke.py
  18. python3 scripts/check-site-ux.py — horizontal nav present, single <main id="main">, breadcrumb landmark, no duplicate README.md family rail bug (see forge-autodoc lenses_split_family_pages directory scope).
  19. IA manifest
  20. If you changed handbook sections, update docs/site-nav.yaml in forge-fleet and rebuild; confirm More dropdown lists Maintainers / Design / Changelog only (no mega-menu of all chapters).
  21. Tagging / comms
  22. Mention doc-affecting commits in CHANGELOG.md (### Host operator when needed).