EmDash 1.1 arrived on October 2, 2026, only a few days after the stable 1.0 launch. Rather than reinventing the CMS, it concentrated on everyday editorial work: planning publications, creating richer pages and making common site operations more reliable.
For anyone evaluating EmDash as a publishing platform, these are more meaningful changes than a long list of minor interface fixes. They affect what editors can do without asking a developer to intervene.
The publishing calendar is the headline feature
A new publishing calendar brings together published content, scheduled posts and scheduled updates. Editors can use a month view or an agenda, filter by collection and locale, and inspect a piece of content's publishing timeline.
Someone with the relevant publishing permissions can reschedule content or publish an overdue entry. Calendar entries use the site's time zone, helping teams avoid ambiguity when contributors work in different regions.
Why is this useful? A blog with two posts a month might manage perfectly well without a calendar. A publication with multiple authors, languages or planned updates needs to know what is going live and when. The calendar turns that information into a visible workflow rather than a set of separate entry settings.
It does not replace a full editorial approval system or guarantee that a team will publish consistently. It makes the schedule easier to see and manage.
Richer HTML and iframe blocks
EmDash 1.1 expanded what editors can place inside Portable Text content. New HTML blocks created through the editor can use separate HTML, CSS, JavaScript and preview tabs, with isolated iframe rendering by default. This helps separate embedded code from the rest of the page.
An iframe block also lets editors embed supported third-party pages, including common video services, using an embed code or URL.
There are operational details worth noting:
- Isolation is not the same as total safety. People permitted to edit and publish blocks still need appropriate editorial trust and review controls.
- Content security policies matter. A site's CSP may need adjustments for approved iframe destinations and isolated content.
- Custom renderers need testing. If a theme overrides EmDash's standard Portable Text or HTML rendering, it may need support for the newer block behavior.
This matters to site owners because richer content is only a benefit if it renders reliably after publication. Developers should test an actual published page, not just the editor preview.
Images are easier to work with
The release made image authoring more direct. Editors can paste or drop images into rich text, then use a consolidated toolbar to manage alt text, alignment, captions and replacement.
It sounds modest, but image handling is one of the places where a CMS can create friction. A straightforward image workflow makes it easier for nontechnical editors to produce posts with useful alternative text and consistent formatting.
An experimental feature for browser agents
EmDash 1.1 also introduced an experimental WebMcpSearch component. Where supported, it allows a browser-based agent to search published content through a read-only tool.
This is not the same as giving a public AI agent permission to edit your site. It is a way to expose selected published information for search. The underlying browser capability was experimental at release, so treat it as an emerging integration rather than an essential production feature.
For developers interested in agent-friendly sites, this is a useful sign of the direction EmDash is taking. Our introduction to EmDash covers the broader architecture.
Less visible fixes that matter to hosting
EmDash 1.1 also improved redirect handling, collection pagination with empty sort fields, request paths for images and menus, and several cache-related behaviors.
These fixes are rarely the subject of a flashy product announcement. Yet they can matter more to a live website than a new toolbar button. A redirect that behaves consistently or a list that does not skip entries is the sort of reliability improvement visitors never notice—because everything works.
The practical lesson is to read beyond each release's headline features when deciding whether to upgrade.
Should you upgrade to EmDash 1.1?
For an independently managed EmDash 1.0 site, version 1.1 introduced useful editor improvements. But the release should still go through a normal update process: backup, compatibility check, deployment and validation.
If your site uses custom renderers, plugins or a restrictive CSP, pay particular attention to the new embedded-block behavior. The official release notes explain those compatibility considerations. If a hosting provider manages your installation, confirm how and when it rolls out core updates rather than assuming every site automatically runs the newest version.
EmDash 1.1 demonstrated that the project was moving quickly beyond a stable launch toward a more complete publishing experience. Subsequent releases continued that work, particularly with the redesigned editor in EmDash 1.2.
For the infrastructure side, compare managed and self-hosted EmDash and see what DashHarbor manages.
