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.
Guides
Converting a static HTML or Figma design into a WordPress theme is one of the most requested skills in WordPress development. The traditional path - splitting index.html into header.php, footer.php, and index.php, then wiring in WordPress template tags - works, but produces fragile, inconsistent output when done manually.
A WordPress PHP theme needs the same content as your static design, but delivered dynamically. Static text becomes template tags or custom field calls. Hard-coded image paths become get_template_directory_uri() references or ACF values. Navigation becomes wp_nav_menu(). The core files every WordPress theme needs are style.css, index.php, header.php, footer.php, page-{slug}.php, and functions.php.
Frontmatter Solo generates the PHP partials and page template stubs, plus a variable contract (INTEGRATION.md) listing every $fm['props'] variable that needs to be populated. Your WordPress developer handles functions.php, WordPress hooks, and data wiring with ACF, post meta, or WP_Query.
Astro is the intermediate step that keeps the contract explicit: typed Props interfaces tell you what is required, what is optional, and what gets mapped into $fm['props']. The result is predictable output, not a theme whose naming depends on who converted it. Solo can also generate a manifest and integration guide that make the wiring obvious before anyone touches WordPress.
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.
A practical guide to converting Astro components into WordPress-compatible PHP templates — partials, page templates, and variable wiring — without a full rewrite.
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 convert Astro components to plain PHP include-based templates — without a framework, without a runtime, and without rewriting your frontend structure.
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.