Cloudflare dropped EmDash on April 1st. Half the web thought it was a joke. But the CMS is real, and it’s open source under MIT license. That license matters more than most people realize. It means anyone can fork it, extend it, and contribute back without legal headaches. And the community is already doing that.
The core EmDash CMS ships with TypeScript, Astro, and a plugin sandbox. That’s a solid foundation. But the real value will come from what the community builds on top. Here are seven contributions — some already landed, others emerging — that make EmDash more than just a WordPress clone with better security.
The combination of MIT licensing and dynamic workers creates a market dynamic that WordPress never had.
1. Gutenberg Editor Port (from a Pantheon Product Manager)
Within hours of the EmDash launch, a product manager at Pantheon opened a pull request to port the Gutenberg block editor. The PR imports WordPress’s block editor into EmDash’s admin interface. It’s not merged yet — the EmDash team said they likely won’t merge it — but the contribution itself proves something. Developers with WordPress experience see EmDash as a platform worth investing in.
The port demonstrates that you can take familiar editing tools and drop them into a modern, sandboxed architecture. Even if the official EmDash team goes a different direction, the PR sets a precedent. Community members can build custom editors that fit their workflows, without waiting for the core team.
2. Italian Language Translation (by dev86dev)
A developer known as dev86dev submitted a pull request adding Italian language support. The PR was still pending at the time of recording, but an automatic merge bot was set to approve it after a week of inactivity. This is a small contribution — language files are straightforward — but it highlights how MIT licensing and a welcoming GitHub repo lower the barrier.
Localization is often an afterthought in new CMS projects. EmDash shipped with English only. The community stepped in to fill the gap. Expect more languages to follow as the project gains traction.
3. Plugin: Email Notification on Content Publish
The official EmDash documentation includes a working example plugin that sends an email when content is published. The plugin declares two capabilities: read:contentcodecode and email:sendcodecode. That’s it. No database access, no file system, no external network calls.
The code itself is a community contribution — it was written as part of the open-source demo. But the real contribution is the pattern. It shows how to build a secure plugin using dynamic workers. Any developer can copy this pattern to create their own plugins without worrying about security holes. The example is simple, but it’s a template for an entire ecosystem.
4. WordPress Import Tool (Official, but Community-Enhanced)
EmDash ships with a built-in WordPress migration tool. You can upload a WXR export file or connect directly to a WordPress site using a plugin. The tool maps Yoast SEO fields, custom post types, and media.
This is officially part of the core CMS, but the community has already started enhancing it. One contributor added support for importing ACF field groups. Another improved the handling of large media libraries. The import tool is one of the most critical features for anyone considering a switch, and community patches are making it more reliable.
5. Theme Starter: Portfolio Template
EmDash comes with three starter templates: blog, marketing site, and portfolio. The portfolio template includes project content types, custom fields for client name and year, and a contact form. It’s responsive and supports dark mode.
The templates are part of the core distribution, but they were built using the same tools the community will use. A developer can fork the portfolio template, customize it with Tailwind and TypeScript, and sell it as a premium theme. The MIT license allows that. WordPress themes under GPL had to be open-source. EmDash themes can be closed-source, which opens commercial opportunities.
6. MCP Server Integration for AI Agents
EmDash ships with a built-in Model Context Protocol (MCP) server. This allows AI coding agents like Claude, Cursor, or GitHub Copilot to interact directly with the CMS. The agent can create content types, migrate themes, or bulk-edit posts using natural language.
The MCP server is core, but the community is contributing agent skill files — structured documentation that tells AI agents exactly how to operate the CMS. One community member published a skill file for automated SEO audits. Another created a skill for generating custom field schemas from natural language descriptions. These skills make EmDash more accessible to non-developers and reduce the learning curve.
7. Dynamic Workers as a Platform for Plugin Security
This is the contribution that experienced practitioners will recognize as the most important. Dynamic workers are not a plugin you install. They are the runtime environment that makes EmDash’s security model possible. The community’s contribution is in adopting and extending this model.
Early adopters are already building plugins that run inside V8 isolates. One developer created a plugin that validates user-submitted content against a custom profanity list — without ever accessing the database directly. Another built a plugin that sends analytics data to a third-party service, but only after declaring http:postcodecode as a capability.
The dynamic worker architecture means plugins cannot escalate privileges. A plugin that says it only reads content cannot write. A plugin that says it only sends email cannot read your user table. This is a fundamental shift from WordPress, where every plugin has full access to everything.
The community’s real contribution here is proving the model works in practice. Each plugin built with dynamic workers is a test case that validates the architecture.
The Strongest Counterargument — and Why It Fails
The most common objection to EmDash is that its ecosystem is too small to matter. WordPress has 60,000 plugins. EmDash has a handful. No WooCommerce, no Elementor, no Yoast. For any business that relies on those plugins, EmDash is a non-starter today.
That argument is true for today. But it misses the trajectory. The WordPress ecosystem took 20 years to build. EmDash is two months old. The community contributions listed here — Gutenberg port, Italian translation, email plugin, import tool enhancements, theme starters, MCP skills, dynamic worker plugins — are all from the first weeks. The rate of contribution is accelerating, not slowing.
History shows that ecosystem adoption follows architecture quality. WordPress won because its plugin architecture was simple enough for anyone to write a plugin. EmDash wins because its plugin architecture is secure enough for anyone to trust a plugin. The MIT license removes the GPL friction that kept commercial developers away from WordPress. And the AI-native MCP server means agents can generate plugins faster than humans can write them.
The ecosystem is small. But it is growing, and the foundation is stronger than WordPress ever had.
A New Idea: The Plugin Marketplace That Could Emerge
None of the current community contributions have addressed one crucial gap: a centralized plugin marketplace. WordPress has wordpress.org/plugins. EmDash has nothing comparable. Yet.
The combination of MIT licensing and dynamic workers creates a market dynamic that WordPress never had. Developers can sell plugins with any license they choose. They can charge per site, per month, or per use via the built-in 402 payment protocol. They don’t need to give code away for free.
This could lead to a marketplace that looks more like the Apple App Store than the WordPress plugin directory. High-quality, audited plugins with clear capability manifests. Users install a plugin, see exactly what it can access, and pay directly for the value it provides.
The first community contributions are already pointing in that direction. The Gutenberg port shows that established WordPress developers are willing to build on EmDash. The dynamic worker plugins show that the security model works. The MCP skills show that AI agents can accelerate development.
The marketplace will not appear overnight. But the seeds are there. And the community is planting them faster than anyone expected.
- What is the Gutenberg Editor Port contribution to EmDash?A Pantheon product manager opened a pull request to port WordPress's Gutenberg block editor into EmDash's admin interface, demonstrating developer investment in the platform.
- How does the MIT license benefit EmDash community contributions?The MIT license allows anyone to fork, extend, and contribute to EmDash without legal restrictions, encouraging a wide range of community-driven enhancements.
