Astro Build Standards docs

Pre-launch#

[checklist.pre-launch]Checklist

Executable form: the launch skill (guardrails.skills), which runs this list in staging or production mode against the built output. Run it, then work the report; this list stays the source of truth for what is checked.

  • npm run check clean (astro check + build)
  • Real domain set in data/site.ts; the config guard passes (seo.identity)
  • Budgets met on home + 2 representative templates (perf.budgets)
  • All active data-themes render correctly; no contrast regressions
  • Sitemap generated + filtered; robots.txt correct for production
  • AI crawlers allowed, or any exclusion recorded as a deliberate client decision (seo.ai-crawlers)
  • Staging/preview is protected by seo.staging method 1–4 β€” not robots.txt alone; production headers verified to not carry noindex
  • Migrations: public/_redirects maps every old URL β†’ new
  • public/_headers: /_astro/* immutable cache + security headers
  • Analytics gated behind consent where required; real IDs via env
  • Form endpoint meets components.forms security requirements; real email received; failure alerting live
  • Production build excludes demo routes (plain npm run build logs "Demo routes excluded")
  • 404 page present and styled; favicons + OG images in place
  • npm run spellcheck clean sitewide, including data/site.ts strings, meta descriptions and OG copy (content.copy)
  • Production deploy verified on the real host β€” routing, forms, images
  • Git history committed under the correct author identity; starterVersion recorded