Astro Starlight
Astro Starlight powers this developer support site.
What It Owns
Section titled “What It Owns”apps/support-devrenders concise internal docs for local setup, feature orientation, dependency maps, workflows, auth, connectors, and platform architecture.- Starlight owns docs navigation, content collections, Markdown/MDX rendering, search, and the support-site shell.
- Support-dev does not own canonical product requirements. It points to the relevant specs, source files, and official dependency docs.
Architecture Decision
Section titled “Architecture Decision”Decision: use Astro Starlight because support-dev is a docs-first site that should be fast, readable, and easy to maintain without becoming a custom Nuxt app or a second product surface.
The site is intentionally an orientation layer: explain what the repo contains, why the pieces exist, and the high-level flow. Link to canonical specs and source instead of duplicating them.
How To Upgrade
Section titled “How To Upgrade”Astro’s official upgrade flow is @astrojs/upgrade. In this Bun repo, run:
bunx @astrojs/upgradeThen keep Starlight and Astro check packages aligned:
cd apps/support-devbun update astro @astrojs/starlight @astrojs/checkAfter any upgrade, run:
bun run --cwd apps/support-dev check-typesbun run --cwd apps/support-dev buildCurrent Limits
Section titled “Current Limits”- Do not add support-dev pages for random task history, temporary notes, or implementation dumps.
- Do not copy long
docs/features/**sections into support-dev. Summarize and link. - Use screenshot placeholders instead of fake screenshots when the UI state is not captured yet.
Canonical Sources
Section titled “Canonical Sources”apps/support-dev/apps/support-dev/AGENTS.mdapps/support-dev/astro.config.mjsapps/support-dev/package.jsondocs/AGENTS.md