Your site runs: solve one specific task, step by step.
Our public pages sit in Cloudflare's edge cache for five minutes, yet a published fix shows up right away, because EmDash purges by cache tag when you publish, and editors keep their Edit button. The five minutes are just the safety net for a purge that doesn't happen. How much faster the pages get, I'll measure after launch.
The WordPress import brings every ACF value along, but repeaters arrive split up and images and relationships point to old WordPress IDs. I show how a small script turns them into real EmDash fields, and what's still manual work.
Let Wrangler create D1 and R2 on your first deploy and Cloudflare picks where they live, for good. If the database ends up in North America, every uncached page pays about 140 ms per query from Europe. Create both yourself first, with --location weur. If you're past that point, read replication helps with reads, but only a move fixes it.
EmDash's admin has no update button. An update is a deployment. I updated a site on Cloudflare and rolled it back again, and I walk you through every step, with timings and what happens to your database along the way.
An EmDash site needs backups too. I show you what the built-in backup does, what D1 Time Travel, the site package and a SQL dump cover, and which one actually gets you back on your feet.