Architecture documentation only stays useful if it's easy to write, review, and keep in sync with the code — which requires treating docs as a first-class, versioned part of the repository rather than an external wiki or slide deck.
What was done
Set up a Starlight-based (Astro) documentation site inside the monorepo (docs/)
Structured content under docs/src/content/docs/, with dedicated sections for architecture (ADR/ADM) and getting-started guides
Ensured documentation changes go through the same PR review process as code changes, per the governance model
Outcome
Documentation site scaffolded and building successfully under docs/
Architecture documentation (ADRs, ADM) and getting-started guides (installation, project structure, roadmap) live in this system
Related
docs/astro.config.mjs
docs/src/content/docs/
## Context
Architecture documentation only stays useful if it's easy to write, review, and keep in sync with the code — which requires treating docs as a first-class, versioned part of the repository rather than an external wiki or slide deck.
## What was done
- Set up a Starlight-based (Astro) documentation site inside the monorepo (`docs/`)
- Structured content under `docs/src/content/docs/`, with dedicated sections for architecture (ADR/ADM) and getting-started guides
- Ensured documentation changes go through the same PR review process as code changes, per the governance model
## Outcome
- Documentation site scaffolded and building successfully under `docs/`
- Architecture documentation (ADRs, ADM) and getting-started guides (installation, project structure, roadmap) live in this system
## Related
- `docs/astro.config.mjs`
- `docs/src/content/docs/`
Ninosaurier
added this to the v0.1.0 - Phase 1: Groundwork milestone 2026-07-22 16:20:46 +00:00
Ninosaurier
self-assigned this 2026-07-22 16:20:46 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
Architecture documentation only stays useful if it's easy to write, review, and keep in sync with the code — which requires treating docs as a first-class, versioned part of the repository rather than an external wiki or slide deck.
What was done
docs/)docs/src/content/docs/, with dedicated sections for architecture (ADR/ADM) and getting-started guidesOutcome
docs/Related
docs/astro.config.mjsdocs/src/content/docs/