astro-ops

# Astro Operations > Facts verified as of 2026-07. Comprehensive patterns for Astro framework development: islands architecture, content collections, rendering strategies, view transitions, and multi-platform deployment. ## Rendering Strategy Decision Tree ``` Which rendering strategy? │ ├─ Is content mostly static (blog, docs, marketing)? │ ├─ YES → Does it change less than daily? │ │ ├─ YES → SSG (output: 'static') │ │ │ Fastest TTFB, CDN-cacheable, zero runtime cost │ │ └─ NO → Hybrid (output: 'hybrid') │ │ Default static + opt-in SSR per route │ └─ NO → Does every page need personalization? │ ├─ YES → SSR (output: 'server') │ │ Dynamic per-request, auth-aware, real-time data │ └─ NO → Hybrid (output: 'hybrid') │ Static shell + server islands for dynamic parts │ ├─ Does the app need real-time interactivity (dashboard, SPA)? │ ├─ YES → Is it a full SPA with client-side routing? │ │ ├─ YES → Consider React/Vue SPA instead, or Astro + client:only │ │ └─ NO → Hybrid + islands architecture │ │ Interactive islands in static pages │ └─ NO → SSG (output: 'static') │ ├─ Build time concerns (>10k pages)? │ ├─ YES → Hybrid with on-demand rendering │ │ Prerender popular pages, SSR the long tail │ └─ NO → SSG handles it fine │ └─ Need edge computing (low latency globally)? ├─ YES → SSR + Cloudflare/Vercel Edge adapter └─ NO → SSR + Node adapter or SSG ``` ### Configuration ```typescr...