Astro

Astro is strongest when most CMS-backed pages are static, so the advanced work is about keeping that static surface large while isolating the few cases that need runtime behavior.

Static generation strategy

• prerender content-heavy routes from CMS data and reserve server endpoints for preview or rare lookup flows;
• generate locale-specific paths from a single authoritative slug query;
• keep shared collections for navigation, SEO, and reusable blocks small and stable; and
• precompute derived artifacts like sitemaps, feeds, and landing page indexes during build.

Preview and editorial flow

• use server-only preview endpoints for draft reads;
• prevent draft-only content from leaking into the static build;
• make rich media rendering deterministic so editorial changes do not alter layout unexpectedly; and
• define which content model changes require a full rebuild instead of selective invalidation.

Operational guardrails

• watch build duration as route counts grow;
• keep route-generation queries separate from full page queries;
• validate asset references before generation starts; and
• document which routes are truly static versus backed by Astro server features.