Engineering · Oct 19, 2026
Laravel + Astro: a clean split
Why separating your CMS API from a content-first frontend keeps marketing sites fast and editable.
Laravel is excellent at structured content, auth, and admin workflows. Astro is excellent at shipping fast, content-heavy pages with minimal client JavaScript.
The pattern
• Laravel exposes JSON for posts and projects
• Astro fetches that data at build or request time
• Editors stay in Laravel; visitors stay on a static-friendly frontend
Keep the CMS boring
Structured models, predictable endpoints, and a calm admin beat clever one-offs. Boring systems are editable systems.
Keep the frontend thin
Fetch at build or request time, render HTML, ship almost no client JavaScript. Marketing pages should feel instant on mid-range phones.
When it shines
Personal sites, agency portfolios, and marketing properties that need a real CMS without dragging a heavy SPA into every pageview.
Trade-offs to expect
You own the glue between API and pages. Cache thoughtfully, version your content contracts, and fail soft when the CMS is briefly down.
Availability
This pattern works wherever you can run Laravel and a static-friendly frontend host — Vercel, Netlify, or a simple VPS with a reverse proxy.