Content management systems have a curious approach to teamwork.
Two people want to edit the same article. So the software lets one person work and asks the other to contemplate their life choices.
You can open the article read-only, take over the editing session or, if you're feeling particularly adventurous, send your colleague a message asking whether they're nearly finished.
It's not exactly the collaborative future of publishing.
EmDash 1.5 has a rather better idea.
The latest release introduces real-time collaborative editing, allowing multiple people to work on the same content simultaneously. You can see who's editing, where they're working and watch changes appear as they happen.
That's the headline feature, but there's quite a bit more going on. The block editor has had a substantial overhaul, administration interfaces are now customisable, there's a built-in SMTP email provider, and new websites start life in staging mode.
There are also some useful improvements under the bonnet for developers, including better image handling, configuration validation and more flexible content management.
Let's have a look at what's changed, and whether any of it is worth getting excited about.
1. Real-time editing: the end of the CMS waiting room?
This is the big one.
Until now, EmDash has used editing locks to prevent two people from accidentally overwriting each other's work. One person opens an entry and gets to edit it. Everyone else gets the digital equivalent of a ticket from the deli counter.
You can open the entry read-only or take over the editing session.
Perfectly sensible if you're trying to prevent content from disappearing. Slightly less convenient if you actually want people to work together.
EmDash 1.5 introduces optional real-time co-editing.
Multiple editors can now work on the same entry simultaneously. Each person can see the other editors' avatars, identify which fields they're working in and see their cursors inside rich text.
Changes to rich text are merged as people type. The undo function also knows who made which changes, so undoing your own work doesn't reverse somebody else's contribution.
That's a rather important distinction. Collaborative editing is considerably less useful if your colleague can accidentally delete an hour of your work by pressing Ctrl+Z.
What's happening behind the scenes?
EmDash creates a shared editing room for each content entry.
Changes are saved together, while retaining the normal permissions, validation, hooks and revision history.
It also means that changes don't have to originate from somebody sitting in front of the administration interface.
Changes made through the REST API, MCP, CLI, visual editor and plugins can appear in editors that already have the entry open.
Think about the implications of that for a moment.
An editor could be reviewing an article while an automated process updates related information through the API. A developer might be working through an MCP connection while somebody else is editing the content.
The CMS now has a mechanism for coordinating those activities.
That's particularly interesting as more websites start incorporating AI agents and automated publishing workflows. Content management is increasingly becoming a job shared between humans and software.
What if somebody loses their connection?
EmDash has thought about that too.
After five seconds without a connection, the editor displays an Offline indicator. People can continue typing, with changes merging when the connection returns.
Publishing, previewing and other operations remain unavailable until the connection is restored.
If changes cannot be merged, they're preserved as recovery revisions rather than silently disappearing.
There are still limitations. Simultaneously moving or deleting a block while somebody else is typing inside it can cause conflicts. Not every possible editing operation can be merged automatically.
That's reasonable. Software developers haven't yet worked out how to make two people simultaneously move the same paragraph to different places without somebody becoming annoyed.
Turning it on
Co-editing is disabled by default.
To enable it, add the following option to your EmDash configuration:
emdash({
coEditing: true,
});Collections need revision support, and the hosting environment must support the required editing rooms.
Cloudflare Workers installations need an EMDASH_ROOMS Durable Object binding and the appropriate Worker exports. Node.js installations have their own WebSocket and reverse proxy requirements.
New Cloudflare sites created from the 1.5 templates already include the necessary infrastructure.
Existing installations need to be configured before co-editing can work.
See the official Cloudflare co-editing documentation.
2. The block editor gets a proper makeover
If you've ever maintained a website built around reusable content blocks, you'll know that editing a complicated page can occasionally resemble an archaeological expedition.
You know the call-to-action is somewhere below the hero section, probably underneath a collection of testimonials and a pricing table.
You just have to find it.
And having found it, you discover that you actually wanted to change the block immediately above it.
EmDash 1.5 gives the block editor a substantial overhaul.
Instead of presenting every block as another enormous form to scroll through, the new interface displays blocks on a single sheet.
Blocks start collapsed, showing their type, a summary of their contents and a thumbnail where an image is present.
You can expand individual blocks, expand everything or collapse everything.
Each block also has a menu providing options to:
- Add blocks above or below.
- Duplicate existing blocks.
- Move blocks up or down.
- Move blocks to the beginning or end.
- Delete blocks.
There are also keyboard shortcuts, drag controls and touch-friendly interfaces.
Lists get a bit more intelligent
The redesign also changes how repeater fields inside blocks are displayed.
Rather than treating every list as the same type of form, EmDash chooses a layout based on the fields it contains.
Simple lists of text become type-in lists, where pressing Enter creates another item.
Lists containing a small number of compatible fields can become editable tables.
More complicated lists use expandable items with summaries and thumbnails.
This is a welcome change. A list of three prices doesn't need to be presented as three separate pages of form fields. Sometimes a table really is just a table.
Better validation
The new editor also checks block fields against the server's validation rules.
This includes required fields, character limits, patterns, number ranges, choices, links and repeater constraints.
When saving or publishing, EmDash identifies problems and takes the editor directly to the relevant field.
Autosave also pauses when a block contains invalid information, explaining what needs attention.
Importantly, this redesign doesn't change the underlying stored content, API, block type schemas or how websites render their existing blocks.
Your existing blocks don't need rebuilding just to benefit from the new editor.
For developers maintaining custom blocks, that's particularly useful.
3. Your administration interface, your rules
Another addition is Settings > Sidebars.
Different people use different parts of a CMS. An administrator might spend most of their time managing settings and plugins, while a content editor might spend almost all their time writing articles.
Previously, everybody essentially had the same navigation arrangement, subject to the website's configuration.
EmDash 1.5 allows individual users to customise their own administration interface.
Users can:
- Hide navigation entries they don't need.
- Reorder navigation items within their existing groups.
- Reorder sections in the content editor's settings sidebar.
- Restore the original arrangement.
- Undo changes to their layout.
Preferences are saved against the user's account, so the same arrangement follows them between browsers.
There are a couple of sensible restrictions. The Dashboard always stays first and visible, and the Publish section cannot be hidden.
The distinction between personal preferences and administrator configuration is important here.
The existing admin.hiddenNavItems setting still hides entries for everyone. The new feature lets individual users organise their own workspace without changing anybody else's.
It's not exactly the sort of feature that gets people jumping up and down at a software launch.
But neither is having to click through seventeen navigation items to find the one you use every morning.
4. Revision history becomes considerably more useful
Autosave is wonderful.
Until it isn't.
There's something particularly unpleasant about discovering that the version you deliberately saved has been replaced by an automatic save made thirty seconds later.
EmDash 1.5 fixes that behaviour.
An autosave now replaces the previous version only when that version was also an autosave. Versions created through the manual Save operation, and other versions generated by EmDash itself, are preserved.
Revision history also becomes more informative.
If several people have contributed to an article, the revision can identify everyone who edited it since the preceding version.
The publishing confirmation can also identify everyone who has made changes since the last published version.
Recovery revisions
The release introduces recovery revisions, which preserve unsaved editor fields in the revision history without changing the current draft or published version.
If an editing operation cannot be merged successfully, there's somewhere to recover the work.
This is particularly useful alongside collaborative editing, where multiple people may be working on the same entry.
The underlying principle is simple: if somebody has spent an hour writing something, the CMS should make a reasonable effort not to lose it.
An apparently radical concept, I know.
5. New websites now start in staging mode
Here's another practical improvement.
Sites created through the EmDash setup wizard or setup API now start in staging mode.
Pages that use EmDash's EmDashHead component receive noindex, nofollow instructions, keeping them out of search engine indexes until the administrator is ready to launch.
The administration interface also displays a Staging indicator.
When the website is ready, an administrator can select Go Live under:
Settings > General > Site Status
The site can also be switched back into staging mode.
There is one important distinction.
Staging mode controls search engine visibility. It doesn't password-protect the website or prevent visitors from accessing its pages.
Existing websites aren't affected by this change. The new default applies to sites created through the setup process.
For developers creating multiple websites, particularly through automated provisioning or templates, this is a useful safeguard.
Nobody particularly enjoys discovering that Google has indexed the unfinished website they were building on Friday afternoon.
6. Built-in SMTP email support
EmDash 1.5 also introduces something website owners have been asking for: a built-in SMTP email provider.
Previously, developers often needed an additional plugin or a custom integration to send email through an external SMTP service.
Now EmDash can connect directly to standard SMTP providers.
Supported examples include:
- Brevo
- Microsoft 365
- Fastmail
- Amazon SES
- Self-hosted Postfix servers
SMTP can be configured through Settings > Email or through environment variables.
The implementation supports TLS connections and standard SMTP authentication methods.
It refuses port 25, so you'll generally be using port 465 or 587.
For Cloudflare Workers, the implementation requires the nodejs_compat compatibility flag.
There's also an important security detail. When SMTP settings are saved through the administration interface, EmDash encrypts the password using EMDASH_ENCRYPTION_KEY.
Why does this matter?
Because email is one of those things that every website needs eventually, but which somehow manages to become an afternoon of configuration, plugins and API keys.
Having a standard SMTP option built directly into the CMS removes another unnecessary dependency.
For smaller websites, that's a welcome improvement.
See the EmDash email documentation.
7. Developers get some useful new toys
There are several other changes in 1.5 that won't necessarily excite somebody who just wants to publish a blog post.
Developers, on the other hand, will probably appreciate them.
Configuration errors are caught earlier
EmDash now checks the types of options supplied to emdash() in astro.config.mjs.
Previously, an incorrectly typed value could be silently ignored or cause problems later.
Now invalid configuration values can stop development, build and sync operations with an error identifying the offending option.
For example, supplying a string where a boolean is expected will produce an error rather than allowing the problem to wander off and cause trouble somewhere else.
Unrecognised top-level options also generate warnings, with suggestions when the supplied name resembles an existing setting.
This is the sort of improvement that saves developers from spending an hour debugging a problem caused by one misplaced quotation mark.
More flexible publication dates
Collections can now use EmDash's existing system dates as their date field.
The supported options are:
publishedAtcreatedAtupdatedAt
This allows developers to display and sort content using its actual publication date without creating duplicate custom fields.
The setting is available through the existing content type configuration.
A small change, but a useful one.
Better control over scheduling
A new no-scheduling collection support flag allows developers to disable scheduling for specific collections.
This is useful when certain content types should only be published immediately or managed through another workflow.
Scheduling remains enabled by default, and existing scheduled content continues to run.
One detail worth noting: the older scheduling support value is now deprecated and no longer controls whether scheduling is available.
Developers who previously relied on omitting that value to disable scheduling should use no-scheduling instead.
Local images in seed files
EmDash 1.5 introduces $media.file support in seed files.
This allows developers to reference local image files alongside their seed data instead of having to make those images available through an external HTTP URL.
For example, a template can include an image in its own assets directory and reference that file during import.
There are some restrictions. Files must remain within the seed directory, and importing local files requires filesystem access at the time the seed is applied.
For people building and distributing website templates, this is a useful improvement.
It makes packaging content and media together considerably more straightforward.
Modern image formats
The Image component from emdash/ui now supports selecting output formats.
Developers can request modern formats such as AVIF and WebP, with a fallback format.
For example:
<Image
image={post.data.featured_image}
width={1200}
height={675}
formats={["avif", "webp"]}
/>The component generates a <picture> element when multiple formats are requested.
There have also been improvements to image upload processing.
EmDash can now generate image placeholders from small browser-generated thumbnails instead of repeatedly decoding full-resolution originals.
This reduces unnecessary CPU work during uploads and enables blurhash and dominant-colour placeholders for formats including WebP and AVIF.
There's also a new imagePlaceholders configuration option, allowing developers to disable placeholder generation across the site if they need to conserve CPU resources.
8. A few things to check before upgrading
As with any substantial CMS release, there are some things worth checking before updating an existing production installation.
Co-editing infrastructure
Co-editing is optional. If you want to enable it, make sure your hosting environment supports the required editing rooms and WebSocket connections.
Cloudflare package versions
Keep emdash and @emdash-cms/cloudflare on matching versions. The Cloudflare adapter now declares an exact matching peer dependency.
Configuration
Review your existing emdash() options. Incorrectly typed values that were previously tolerated may now prevent the site from building.
Scheduling
Check collections that previously relied on the deprecated scheduling configuration value.
Sandboxed plugins
There is an additional upgrade consideration for sites using @emdash-cms/sandbox-workerd.
Version 0.9.7 includes a migration for plugin KV storage when a plugin moves between the regular and sandboxed plugin configurations.
This is a coordinated upgrade, not something to casually deploy one component at a time.
The official instructions require a database backup, stopping application instances and plugin jobs, upgrading the packages together, building without starting the application, running the migration and resolving any conflicting KV values before plugins resume writing.
If you use sandboxed plugins, read the official upgrade instructions carefully.
For everyone else, the normal upgrade guidance and project-specific checks still apply.
So, is EmDash getting better?
Yes. And perhaps more importantly, it's getting better in the right places.
The obvious headline is collaborative editing, but I think the improvements to the block editor and revision history deserve almost as much attention.
These are the things that make a CMS pleasant to use every day.
Not another dashboard widget. Not another seventeen configuration options nobody asked for. Just less friction between having something you want to publish and actually getting it published.
Built-in SMTP removes another dependency. Staging mode makes new installations safer from accidental indexing. Better image handling and configuration checks make life easier for developers.
None of these changes will transform every website overnight.
But collectively they show a platform addressing the practical problems that emerge when people actually use it.
EmDash is still young. There are features it doesn't have, integrations that need developing and hosting considerations that shouldn't be ignored.
That's fine. Software doesn't become mature by pretending it already is.
It becomes mature by solving problems, learning from real usage and steadily getting better.
EmDash 1.5 is another step in that direction.
And then there's the hosting...
Of course, getting a CMS installed is only the beginning.
There's infrastructure to manage, updates to apply, backups to maintain, security to monitor and the occasional opportunity to discover that something has gone spectacularly wrong at precisely the moment you were hoping to go to bed.
DashHarbor takes care of the operational side of running EmDash websites.
Managed hosting, automated updates, backups, recovery, monitoring and a protected editing environment.
You concentrate on the website. We'll look after the plumbing.
Create your free EmDash website with DashHarbor.
