{"id":98016,"date":"2026-10-05T15:02:00","date_gmt":"2026-10-05T19:02:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=98016"},"modified":"2026-09-29T07:53:55","modified_gmt":"2026-09-29T11:53:55","slug":"emdash-revisions-content-recovery-98016","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/emdash-revisions-content-recovery-98016\/","title":{"rendered":"Use EmDash’s Revisions to Never Lose Content"},"content":{"rendered":"

You make a change, hit save, and something breaks. A paragraph you spent an hour writing? Gone. A page layout you carefully arranged? Replaced by an earlier, worse version. WordPress users know this pain. EmDash<\/a>, Cloudflare’s new open-source CMS (version 0.1, built in roughly 2 months by Astro core team member Matt Cain), ships with a revision and draft system designed to prevent exactly this. Here’s how it works and how you use it.<\/p>\n

What EmDash’s Revision System Actually Saves<\/h2>\n

Every time you save a page or post in EmDash, the system creates a snapshot. Not just the content body \u2014 the full state including title, featured image, SEO metadata, categories, and custom fields. The source confirms: “we have the revisions. Very nice.”<\/p>\n

In the playground at emdashcms.com (a temporary instance that lasts one hour), revisions are limited. On a real deployed instance, every save generates a new revision entry. Open a published post, make an edit, and the original version stays intact under the revision history. You never overwrite \u2014 you layer.<\/p>\n

The practical difference from WordPress? WordPress also saves revisions, but they live in a separate wp_postmeta<\/code>codecodecodecodecode table that bloats your database. EmDash stores them as structured JSON (portable text format), keeping the data clean and the full history queryable without extra plugin overhead.<\/p>\n

Recover Content from a Previous Revision in 4 Steps<\/h2>\n

Here’s the exact workflow when you<\/a> need to undo a bad edit on a page or post in EmDash:<\/p>\n

    \n
  1. Open the content item from the Posts<\/strong> or Pages<\/strong> section in the admin dashboard.<\/li>\n
  2. Look at the right sidebar panel. You’ll see a Revisions<\/strong> section with timestamps listed in reverse chronological order \u2014 most recent save first.<\/li>\n
  3. Click any revision timestamp. The preview pane loads that exact version of the content: title, body, featured image, and all metadata fields.<\/li>\n
  4. If the preview shows the version you want, click Restore<\/strong>. That revision becomes the current published or draft version.<\/li>\n<\/ol>\n

    What happens to the version you just overwrote? It becomes another revision entry. Nothing is deleted. The system keeps every save you’ve made.<\/p>\n

    This process works for both published content and content still in draft. A post saved five times before publishing has five revision entries you can return to.<\/p>\n

    How Drafts Prevent Publishing Mistakes<\/h2>\n

    EmDash separates draft content from published content at the database level. When you create a new post, it starts in draft status by default. You can save multiple times, make edits across days, and nothing goes live until you explicitly click Publish<\/strong>.<\/p>\n

    The critical detail: EmDash’s draft system supports scheduled publishing<\/strong>. You set a date and time, save as draft, and the system publishes automatically at that moment. If you change your mind before the scheduled time, switch the status back to draft or delete the entry entirely.<\/p>\n

    The front-end editor also respects drafts. Click the Edit<\/strong> button while viewing your site’s front end, and you enter an inline editing mode. Save those edits \u2014 they go to the draft version, not the live version. You preview the changes, then decide to publish or discard.<\/p>\n

    This is the edge case most CMS users miss: editing on the front end should never immediately overwrite the live page. EmDash’s draft-first architecture ensures that.<\/p>\n

    EmDash vs WordPress: Revision Features Compared<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n
    Feature<\/th>\nEmDash (v0.1)<\/th>\nWordPress (6.x)<\/th>\n<\/tr>\n<\/thead>\n
    Revision storage format<\/td>\nStructured JSON (portable text)<\/td>\nSerialized PHP in wp_postmeta<\/code>codecodecodecodecode<\/td>\n<\/tr>\n
    Draft-publish separation<\/td>\nBuilt-in, with scheduled publishing support<\/td>\nBuilt-in, but scheduled publish requires cron<\/td>\n<\/tr>\n
    Front-end inline editing<\/td>\nYes \u2014 edits go to draft, not live<\/td>\nYes (via block editor), but edits apply directly<\/td>\n<\/tr>\n
    Revision restore from preview<\/td>\nClick a timestamp, preview, then restore<\/td>\nClick a timestamp, compare diff, then restore<\/td>\n<\/tr>\n
    Custom post type revisions<\/td>\nSupported natively \u2014 flexible content types include revision history<\/td>\nSupported only if the custom post type explicitly enables revisions<\/code>codecodecodecodecode via register_post_type()<\/code>codecodecodecodecode<\/td>\n<\/tr>\n
    Revision retention<\/td>\nEvery save retained (no built-in limit in v0.1)<\/td>\nConfigurable via WP_POST_REVISIONS<\/code>codecodecodecodecode constant (default: 5 per post)<\/td>\n<\/tr>\n
    AI agent<\/a> access to revisions<\/td>\nMCP server can query and restore revisions programmatically<\/td>\nRequires custom REST endpoint or plugin<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The table shows one clear advantage for EmDash: custom post types get revisions without any plugin. In WordPress, you need to add 'revisions' => true<\/code>codecodecodecodecode to your register_post_type()<\/code>codecodecodecodecode call, and many site owners forget this step. EmDash’s flexible content types (pages, posts, projects, or any custom type you create) all inherit revision support automatically.<\/p>\n

    What Revisions Don’t Cover (Yet)<\/h2>\n

    EmDash is version 0.1. Some gaps exist.<\/p>\n

    First, the playground at emdashcms.com does not<\/a> include full revision history. You can see the system saving in real time, but you cannot browse past revisions in the temporary instance. To test revisions properly, deploy EmDash to a Cloudflare<\/a> Workers account or a local Node.js server.<\/p>\n

    Second, there is no visual diff tool. WordPress shows you what changed between two revisions with highlighted additions and deletions. EmDash shows only the raw restored content. You cannot, as of this beta, compare revision A against revision B side by side.<\/p>\n

    Third, there is no automatic cleanup. Every save becomes a permanent revision. On a site with heavy editing activity, the revision count grows without limit. In WordPress, you can set WP_POST_REVISIONS<\/code>codecodecodecodecode to cap the number. EmDash offers no such setting yet.<\/p>\n

    The Real Safety Net: Combine Drafts, Revisions, and the Import Tool<\/h2>\n

    The most overlooked recovery path in EmDash is the WordPress import tool. If you migrate a WordPress site into EmDash (using the WXR export file or the dedicated export plugin), your entire content history comes with it. Posts, pages, media, custom post types \u2014 all of it. The import maps Yoast SEO fields to EmDash’s built-in SEO fields automatically.<\/p>\n

    This means even if you delete content inside EmDash, you can re-import from your original WordPress export. It’s not a substitute for proper revision history, but it is a hard backup that survives accidental deletion.<\/p>\n

    For production use in 2026, that extra layer matters. EmDash’s architecture is the most coherent challenge WordPress has faced \u2014 the plugin sandbox alone justifies the experiment. But the revision system, like everything else in v0.1, will evolve. Keep a separate backup of your content exports until it does.<\/p>\n","protected":false},"excerpt":{"rendered":"

    You make a change, hit save, and something breaks. A paragraph you spent an hour writing? Gone. A page layout you carefully arranged? Replaced by an earlier, worse version. WordPress users know this pain. EmDash, Cloudflare’s new open-source CMS (version 0.1, built in roughly 2 months by Astro core team member Matt Cain), ships with […]<\/p>\n","protected":false},"author":7,"featured_media":99229,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98016.png","fifu_image_alt":"Use EmDash's Revisions to Never Lose Content","footnotes":""},"categories":[31],"tags":[],"class_list":["post-98016","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98016.png","fifu_image_alt":"Use EmDash's Revisions to Never Lose Content","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98016","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=98016"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98016\/revisions"}],"predecessor-version":[{"id":99230,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98016\/revisions\/99230"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/99229"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=98016"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=98016"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=98016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}