Generating PHP templates from a static HTML design
How to convert a static HTML/CSS design into clean PHP include-based templates - variable contracts, conditional rendering, and how to automate the conversion without rewriting your structure.
All notes
Chronological archive. For the job-based taxonomy, start at the guide hub.
How to convert HTML to Twig templates
A step-by-step guide to converting a static HTML/CSS design into Twig templates - variable mapping, conditional blocks, layout inheritance, and how to automate the whole process.
How to convert an HTML design to WordPress PHP templates
The developer's approach to converting a static HTML/CSS design into WordPress-compatible PHP templates - partials, page templates, variable wiring, and how to skip the manual rewrite.
Validate your Astro project against the Solo contract — for free
solo-check is a free open-source CLI that tells you exactly whether your Astro project is compatible with Frontmatter Solo — before you buy anything.
Astro project delivery checklist — what to ship to your backend developer
A practical checklist for frontend developers delivering an Astro project to a backend team. What to include, what to generate, and what to never hand off manually.
Integrating an Astro frontend with a Symfony backend
How to hand off an Astro project to a Symfony developer — Twig templates, controller variables, and the integration pattern that keeps both sides clean.
Astro PHP templates for WordPress — the clean approach
How to structure PHP templates generated from Astro so they work cleanly with WordPress — partials, escaping, variable passing, and what not to do.
How to generate WordPress-compatible PHP templates from an Astro project
A practical guide to converting Astro components into WordPress-compatible PHP templates — partials, page templates, and variable wiring — without a full rewrite.
Why frontend developers should own the backend handoff
The handoff is not a backend problem. It's a frontend artifact — and the frontend developer is the only one positioned to generate it correctly.
Generating PHP templates from an Astro project
How to convert Astro components to plain PHP include-based templates — without a framework, without a runtime, and without rewriting your frontend structure.
Backend handoff from Astro — the clean way
What a proper Astro-to-backend handoff looks like, what usually goes wrong, and how to structure it so the backend developer can start immediately.
Why “AI-built websites” don’t age well
AI can generate websites in minutes. But when trends, tools, and business models change, content-driven architectures are the only ones that survive.
How to convert an Astro project to Twig templates
A step-by-step breakdown of what it takes to turn Astro components into Twig partials — manually, and with a build-time tool.
Why we don’t ship CMS adapters in the core
CMS adapters create hidden coupling and support debt. Keeping them outside the core is a deliberate architectural choice.
Layout is code, content is data
A simple rule that prevents CMS-driven rewrites: keep layout in code, expose content as structured data.
Why CMS break modern frontends (Astro makes it obvious)
CMS are great at content, but they model structure too late. Astro exposes the mismatch — build-time IR fixes it.