Port a WordPress theme to EmDash

Recreate the theme's relevant layouts and interactions as an Astro site backed by EmDash. Preserve the user's requested visual fidelity and feature scope; do not assume every WordPress template or demo feature belongs in the port.

Load building-emdash-site for current EmDash schema, query, rendering, caching, and seed patterns. When a live reference site is available, use the agent-browser CLI for rendered comparison; run agent-browser skills get core --full for its command reference.

Choose the evidence

Use the best available sources in this order:

1. theme source and theme.json, stylesheets, templates, and functions.php;
2. a live demo at representative desktop and mobile viewports;
3. screenshots or design files supplied by the user;
4. explicit design decisions where the source is ambiguous.

Do not infer that demo content or images share the theme code's license. Reuse an asset only when its license or the user's rights permit it; otherwise use a clearly licensed substitute with similar dimensions and visual weight.

Plan the port

Inventory only the page types, components, responsive states, and interactions needed for the requested site. Map WordPress responsibilities before implementing:

• PHP templates become Astro routes, layouts, and components.
• Custom post types, metadata, and taxonomies become EmDash collections, fields, and taxonomies.
• Theme Customizer values become site settings or explicit project configuration.
• Menu locations become named EmDash menus queried by templates.
• Sidebars and widgets become widget areas or ordinary Astro components.
• Shortcodes and plugin-owned behavior may require a separate plugin migration.

Read WordPress theme concept mapping when translating template hierarchy, functions.php registrations, template tags, hooks, widgets, or reusable blocks.