Frontend/backend handoff
The design is done. The PHP team needs templates, named variables and ownership. This cluster is the map of that handoff.
Then pick Twig or PHP depending on the host.
Astro frontend-to-backend integration guides
These guides explain how a constrained Astro frontend becomes documented Twig, PHP or Grav output — without a second UI rewrite. They are grouped by job, not by publish date.
Existing article URLs stay under /blog/. This hub is the taxonomy. The chronological archive remains at all notes.
Astro to Twig and Symfony
Astro components become Twig partials, layouts and a controller variable contract. Drupal and Craft are secondary notes, not the primary target.
Use the Twig adapter, then Solo, then solo-check before purchase.
Astro to PHP and WordPress
Plain PHP pages, layouts and partials. WordPress is a wiring use case — not a complete theme with hooks or functions.php.
Start from the PHP adapter, then the WordPress guide if that is the host.
Astro to Grav CMS
Turn a developer-controlled Astro frontend into an editable Grav CMS site. Studio is coming soon. The pillar and tutorial are readable without the product.
Read the Grav pillar, then the practical tutorial. Waitlist only — no purchase.
Frontend-driven CMS architecture
Why layout belongs in code, why CMS modeling happens too late, and how a build-time IR keeps the frontend in charge.
Core is the extraction layer. Studio is the planned Grav path.