Skip to content

Astro Implementation Guide - Master Index

This guide provides a structured approach to building high-performance Astro sites through a single progressive path with three natural tiers:

  • Foundation (Phases 0–4): Core setup — everyone starts here
  • Build (Phases 5–8): Make it yours — components, content, QA
  • Polish (Phases 9–12): Production-harden — performance, deployment, docs

Work through phases sequentially and stop when you’ve reached your goals. See ADR-033 for the rationale behind this model (it replaced the earlier MVP/Showcase dual-track model).

Foundation (everyone)
Phase 0: Foundation
→ Phase 1: Content Architecture
→ Phase 2: Design System
→ Phase 3: Tooling
→ Phase 4: Skeleton
Build (make it yours)
→ Phase 5: Components
→ Phase 6: Sections
→ Phase 7: Content
→ Phase 8: QA
Polish (production-harden)
→ Phase 9: Performance
→ Phase 10: Deployment
→ Phase 11: Documentation
→ Phase 12: Post-Launch

Foundation (Phases 0–4) — Everyone does these

Section titled “Foundation (Phases 0–4) — Everyone does these”

Pre-configured in the template. Delivers a deployable site skeleton with no content.

  • Astro + TypeScript + Tailwind + Biome
  • Content Collections schemas
  • Design tokens system
  • Base layouts and structural components
  • CI pipeline

Build (Phases 5–8) — Where you make it yours

Section titled “Build (Phases 5–8) — Where you make it yours”

Scope each phase to your project’s actual needs using the Essential / Recommended / Advanced labels within each guide.

  • UI component implementation
  • Page sections and layouts
  • Content creation
  • Quality assurance

Polish (Phases 9–12) — Production hardening

Section titled “Polish (Phases 9–12) — Production hardening”

Stop here when you need an enterprise-grade deployment.

  • Performance optimization and budget enforcement
  • Deployment configuration
  • Documentation and AI context
  • Post-launch monitoring and maintenance

“Completed” vs “Active” is from your perspective as a cloner, not the template’s. This template already ships a fully-built reference implementation of every phase (44 components, content collections, an e2e suite, performance budgets, CI, and deployment config). The Foundation phases below are marked “Complete” because they’re shared infrastructure you inherit as-is; the “Active” phases are the customization work you do to make the site yours (your components, your content, your QA pass). Read each active phase as a guided walkthrough, using the shipped implementation as the worked example.

PhaseNameScopeStatus
0FoundationEssential✅ Complete
1Content ArchitectureEssential✅ Complete
2Design SystemEssential✅ Complete
3ToolingEssential✅ Complete
4SkeletonEssential✅ Complete
PhaseNameScopeEffortCritical Path
5ComponentsEssential → Advanced2-4 days
6SectionsEssential → Advanced2-3 days
7ContentEssential3-5 days📝
8QAEssential → Advanced1-3 days
PhaseNameScopeEffortCritical Path
9PerformanceEssential1-2 days
10DeploymentEssential1 day🚀
11DocumentationRecommended1-2 days📚
12Post-LaunchRecommended1 day🎯
  1. Review Tech Stack: Check technology choices
  2. Understand Budgets: Study performance targets
  3. Set Up Structure: Follow directory layout
  4. Begin Phase 0: Start with foundation decisions
  5. Stop when done: Each tier has a clear deliverable — ship when it meets your goals

Each active phase includes practical code examples:

NeedEssentialRecommendedAdvanced
InteractivityStatic HTML + CSSCSS + minimal JS for simple statePreact islands where justified
TestingManual checklistPlaywright critical pathsFull e2e suite + a11y checks
ComponentsCore UI onlyExtended component library/showcase style guide + full documentation
DocumentationREADME + basicsAI context updatedComprehensive guides
MonitoringBasic uptimeLighthouse CIRUM + error tracking
  • Changelog: See CHANGELOG.md in the repository root
  • Issues: Create an issue in your project repo
  • Updates: Check monthly for Astro updates
  • Community: Astro Discord