Why Astro?
Why Astro?
Section titled “Why Astro?”The Code portal is documentation-heavy, content-heavy, SEO-driven, and performance-sensitive. Astro keeps most of that experience static and lets interactive tools enter as focused islands when they earn the complexity.
The decision
Section titled “The decision”Use Astro and Starlight for the public intelligence layer. Keep standalone tools such as Live Event Report independently runnable under public/experiments/.
What this makes possible
Section titled “What this makes possible”- Fast delivery of architecture stories and project pages.
- A clear content model without inventing an application backend.
- React or browser islands only where interaction is useful.
- Straightforward Cloudflare Pages deployment.
What it does not solve
Section titled “What it does not solve”Astro does not decide the product story, validate claims, or make a complex tool trustworthy. Those remain content and product decisions. The framework is a good container for the work; it is not the work itself.
WORK WITH RICHIE // SYSTEMS INQUIRY
Build something that can actually be used.
Bring a tangled workflow, technical decision, or ambitious idea. Start by making the problem clear enough to shape.