All posts

Is EmDash a WordPress killer? I moved my 20-year-old blog to find out

I asked on LinkedIn whether WordPress should still be the default CMS. Someone called EmDash a WordPress killer, so I moved my 20-year-old blog to it. Here's what happened.

Blog pages moving from a WordPress stack to an EmDash stack across a global network

A few weeks ago I asked on LinkedIn: Should WordPress still be the default CMS in 2027?

Most replies were the debate you'd expect. One wasn't. Tyler McConville wrote that EmDash, Cloudflare's new CMS, hooked up to a static generator with Claude Code, is "a WordPress killer".

I said I'd build a small proof of concept, mainly to see how the editing side and the upkeep compare to WordPress. Then I raised the stakes: I'd move my own blog and see how it goes.

This is that report.

What I moved

This blog started in December 2005. It ran on WordPress the whole time.

  • 385 published posts, from 2005 to early 2025
  • 5 pages and 771 images
  • 20 years of links on other sites, in search results and in old emails

The last point was the one I cared about most. If old links broke, the move wasn't worth doing.

The new setup:

  • EmDash for content and the admin, on Astro
  • Cloudflare Workers to run the site, D1 for the database, R2 for images
  • Cloudflare Images to resize photos on the fly
  • No WordPress plugins. The only plugin is a small contact form I wrote, and it runs sandboxed.

How it went

It took two long working sessions, a few days apart. The first one built the site and imported everything. The second one was polish and the switch-over.

I was curious more than convinced. EmDash looked interesting, and my blog was the perfect test: old, messy, and mine to break.

Claude Code did most of the typing. I did the thinking: what to keep, what to drop, what "done" looks like. It's like working with a very fast developer who never gets tired, but still needs a lead who checks the work.

WordPress stayed live and untouched until the last step. The switch itself was: delete one DNS record, deploy, move my sign-in to the new domain. If anything had gone wrong, putting that DNS record back would have brought WordPress back.

What surprised me

  • No custom widgets yet. EmDash only has its built-in widget types; custom ones are still a proposal. I built my "Continue reading" section into the theme instead.
  • Imported images lost their sizes. The WordPress importer dropped width and height, so full-size originals were served until we fixed the data.
  • Passkeys belong to a domain. A passkey only works where you created it. EmDash's "Change domain" flow handles the move, but turning off the preview first would have locked me out.
  • Old settings bite back. My analytics doubled after the switch. Cloudflare Zaraz was already sending Google Analytics, and I'd added it again in the theme.
  • It's young. EmDash is at version 1.5. Some WordPress basics don't exist yet, and when the docs run out, you end up digging through its code for answers.

What I got

  • Old links still work. Old post addresses and old image links redirect to their new homes. I dropped WordPress's extra thumbnail copies and a few files that were already missing.
  • Speed: WordPress, behind the same Cloudflare proxy, scored about 60 on mobile and 80 on desktop in PageSpeed. Now it's 96 on mobile and 100 on desktop.
  • SEO 100, with a sitemap Google read on day one: 390 pages.
  • A contact form with spam protection, built as a small sandboxed plugin instead of a heavy form plugin.
  • Images resized on Cloudflare's edge, in WebP or AVIF depending on the browser.

Different things to look after. I swapped one stack for another. Instead of WordPress, PHP and plugins, I now watch EmDash, Astro, Node packages and my Cloudflare setup for vulnerabilities. The upkeep didn't disappear; it moved. What changed is that updates go through my code and get tested before they're live.

Cost: about the same. The Linode VPS for WordPress was $10 a month. Now it's roughly $10 a month on Cloudflare (Workers Paid plus Images). I didn't move to save money.

The editing side

This was half of what I set out to test, and it's the part I like most.

The editor feels like Notion: type “/” to add a block, paste an image and it uploads, everything is a block. I love Notion, so I felt at home straight away.

So, is it a WordPress killer?

Not yet. WordPress is still far ahead on customisation. Twenty years of plugins and themes don't get matched in a year, and today most changes in EmDash happen in code.

But it has real potential. The foundations are right: a clean editor, fast pages by default, plugins that run sandboxed instead of with full access, and it all runs on Cloudflare's network. If the plugin ecosystem grows, it could become a serious choice for client sites too.

For now, my answer to my own LinkedIn question is: not by default. For a developer's own site or a small blog, EmDash already works well. For client sites with editors and plugins, WordPress still earns its place, for now.

Tyler, thanks for the push. Where do you still reach for WordPress?

Category
Tags

Discussion

No comments yet