AI-editable content
Marketing edits copy, swaps images, and reorders sections by chatting with Claude. No CMS UI to learn.
Now booking · Q1 2026
Migrate WordPress to EmDash, the right way
Done-for-you migrations from WordPress + static sites to Astro + EmDash. Your marketing team edits via Claude. We handle the move.
The problem
Two bad options. We're building a third.
Marketing teams want to edit. Devs want a fast site. Most stacks force a trade-off — EmDash doesn't.
WordPress is heavy.
Plugins, page builders, a database, a PHP host — five moving parts to publish a paragraph. Performance suffers. So does the bill.
Static is rigid.
Hand-coded sites are fast, but every copy change is a deploy. Your marketing team files a ticket every time they want to fix a typo.
EmDash splits the difference.
Astro static performance + a content layer marketers can edit through Claude. Files-as-database — no CMS to babysit, no plugin tax.
the approach
Same site, half the moving parts.
A typical migration replaces five things with one folder of Markdown. The rest is muscle-memory.
- step 01 Audit the existing site, plugin inventory, and analytics setup.
- step 02 Model the content as typed EmDash schemas — files, not a database.
- step 03 Port the theme to Astro components, mobile-first, CWV-green.
- step 04 Cut over with redirects. Train the team to edit via Claude.
What you get
A site your team can actually edit.
Four things that hold up the entire engagement.
Sub-1s page loads
Astro + Cloudflare Pages ships static-site speed without giving up a CMS. CWV green at handoff, gated in CI.
Git-versioned, no plugin chaos
Themes are Astro projects in your repo. Plugins are sandboxed Workers with explicit permissions. No more functions.php roulette.
Analytics that actually work
GA4 + GTM + UTM injector wired in by default. Hidden-field capture, CSP-safe tag injection, real events that fire.
TBD: real testimonial
They migrated us off a 12-year-old WordPress install in a month, and our marketing team is now shipping copy changes in five minutes instead of five days.
TBD: real testimonial
The Claude-via-MCP workflow alone saved us from hiring another front-end dev this quarter.
Services
Pick where you are.
Three paths. Same destination — a site you actually want to edit.
migration
WordPress migration
Done-for-you migration from WordPress to Astro + EmDash. Marketers edit via Claude. Devs stop firefighting plugins.
From $3,000 4 weeks
migrationStatic site migration
You hand-coded the site. Marketing keeps emailing you copy changes. Migrate to Astro + EmDash and let them ship without you.
From $1,500 2 weeks
setupVibecode setup
Skip the WordPress migration tax. Greenfield project, Astro + EmDash + Cloudflare, MCP-wired from day one.
From $1,500 1 week
Recent writing
From the EmDash + Astro frontier.
Topics
emdash P1 · cornerstone Featured · emdash
Six weeks evaluating EmDash for production work: what we learned before betting on it
For the agency owner who's read all the EmDash hype and wants the boring version: what we measured across six weeks of building, evaluating, and pitching EmDash work — before any client site went live. The bugs, the gaps, the things we'd wait on, and the things that already work.
More field notes 2 posts · sorted newest
migrations P2 Static site to EmDash: when to skip the migration and just rebuild
For the marketing lead at a small SaaS whose 30-page hand-coded HTML site has become a dev bottleneck: when migrating to a CMS makes sense, when starting fresh on EmDash + Astro is faster, and the surprisingly common third option — leave it alone.
astro P3 Hitting Lighthouse 95 on every page: the Cloudflare Pages performance budget for marketing sites
For the agency owner who keeps losing the 'why is your site faster than ours' argument with prospects: the Lighthouse CI budget config, the JS-shipping rules, and the image pipeline that ship Lighthouse 95+ on every page on Cloudflare Pages.