EmDash 1.2 was released on October 7, 2026. It was a substantial follow-up to version 1.1, with a redesigned editor, native video support, improvements to large content collections and a new workflow for changing a site's domain.

For a developer evaluating EmDash, the most important theme is that publishing and operating a site are becoming less dependent on manual intervention. The changes are practical, although a few still require care during upgrades.

A redesigned content editor

The editor received a more open layout, reducing the feeling of entering data into separate form fields. Formatting tools are easier to reach, and block controls offer familiar actions such as moving, duplicating, transforming and deleting content.

Keyboard navigation also improved. Editors can move between the title and body, create blocks with slash commands and keep the formatting toolbar visible while writing.

Why does this matter? The difference between a CMS used every day and one that is tolerated often lies in small tasks: moving an image, editing a link or adding a list. A better editor reduces the number of occasions when an author needs to ask someone else to fix the layout.

The result is particularly relevant for teams moving from WordPress or another visual CMS. EmDash still has its own content model, but it increasingly offers the editing conveniences people expect. For a broader comparison, see EmDash vs WordPress.

Video blocks inside rich text

Version 1.2 added native video blocks to the Portable Text editor. An editor can choose a video from the Media Library, upload one, or insert it into a post using a slash command.

On the public website, EmDash's standard Portable Text renderer can display the video using a browser player or a provider-specific embed, with a caption.

There are limits to consider. The default maximum upload size documented for the release is 50 MiB, and hosting configurations may set different limits. Media storage, delivery costs and content security policies still need to be planned. A video block improves the publishing workflow; it does not turn a CMS into a full video-streaming platform.

Moving an EmDash site to another domain

A standout change for site owners is the Change domain workflow in Settings. Instead of updating the address in one place and hoping everything else follows, EmDash can check whether the new domain serves the site before switching its configured Site URL.

The new address is used for various site-generated links and metadata, including canonical URLs, sitemaps and relevant email links. The change also accounts for the fact that passkeys belong to their original web origin: people may need to register a passkey for the new address.

This does not eliminate the need to configure DNS or hosting routes. Those still have to point the new domain at the correct deployment. The domain-move feature helps the CMS stay consistent once that setup is in place.

For an SEO-sensitive move, check the canonical URLs and redirects as well as the CMS settings. A correct domain name in the admin does not, by itself, preserve rankings or migrate every old URL.

Better handling of large collections

The admin's content lists gained numbered pagination. Instead of loading a large number of entries at once, an editor can move between pages and adjust the number shown.

Collection sitemaps also gained pagination beyond their earlier size limit. This is largely invisible to a small personal blog, but it matters when a project grows to hundreds or thousands of entries. Developers with customized sitemap routes should review the release notes before updating.

A new EmDash upgrade tool

EmDash 1.2 introduced the upgrade-emdash CLI. Its purpose is to update the project's direct EmDash packages and produce a project-specific upgrade guide, including the relevant changelog items.

For a self-managed site, the official command is:

npx upgrade-emdash@latest

That is an upgrade preparation step, not a substitute for backups or deployment testing. It also targets the latest version available when run, not necessarily 1.2. If you operate a managed site, use your provider's supported update process instead of assuming a locally executed command controls the hosted runtime.

What should site owners check before upgrading?

EmDash's 1.2 release notes flag several details that are easy to miss:

  1. Domain and email settings. Verify the Site URL used for login and notification links.
  2. Plugins and custom blocks. Test any custom video block or plugin lifecycle hooks.
  3. Sitemaps. Review custom sitemap implementations or directly submitted collection sitemap URLs.
  4. Content links. Check templates that build localized URLs from entry IDs.
  5. Deployment behavior. Validate the updated site before switching production traffic.

The official 1.2 release reported no new numbered core database migration, but compatibility checks still mattered.

Why EmDash 1.2 matters for hosted websites

Better editing makes EmDash more approachable, while domain changes and migration tooling address problems that can otherwise turn into support requests. These are encouraging developments for a CMS intended to power real sites.

They also illustrate why hosting remains a separate concern. A CMS update can improve software behavior, but someone still needs to manage deployments, backups, DNS and recovery. Learn more about EmDash hosting on Cloudflare and managed EmDash hosting.

The next major release, EmDash 1.3, focused on revision history, inline editing and Cloudflare database efficiency.

Sources and further reading