{"id":97960,"date":"2026-09-30T00:38:00","date_gmt":"2026-09-30T04:38:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=97960"},"modified":"2026-09-29T08:09:41","modified_gmt":"2026-09-29T12:09:41","slug":"emdash-cms-dashboard-design-choices-97960","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/emdash-cms-dashboard-design-choices-97960\/","title":{"rendered":"EmDash CMS Dashboard: What the Non-Obvious Design Choices Actually Mean"},"content":{"rendered":"

You’ve installed EmDash<\/a>. You’ve clicked through the wizard, set your passkey, and landed on the admin. It looks like WordPress. That’s the point. But the surface familiarity hides decisions that change how you build, deploy, and maintain a site. Here’s what matters beyond the first impression.<\/p>\n

The Dashboard Is a Trap \u2014 But a Useful One<\/h2>\n

The layout mimics WordPress’s left-nav structure. That’s deliberate. The team wanted your muscle memory to transfer. But the similarities end at the navigation.<\/p>\n

Collapsing Content Management<\/h3>\n

Notice the sidebar collapses. That’s not just aesthetic. EmDash treats every section as a first-class citizen, not a plugin afterthought. In WordPress, you manage menus through one interface, redirects through another (often via Yoast or Redirection plugin), and widgets through the Customizer. EmDash consolidates these into logical groups: Content, Manage, Admin.<\/p>\n

The “Manage” section is where the non-obvious<\/a> lives. Redirects, widgets, sections, categories, tags, and bylines live here. Bylines aren’t author profiles \u2014 they’re attribution blocks you can attach to any content type. That’s a hint: EmDash thinks in structured content, not just posts and pages.<\/p>\n

Content Types Are Not Post Types<\/h3>\n

WordPress gives you posts and pages. Custom post types require a plugin like ACF or CPT UI. EmDash bakes this into the core. Navigate to Admin > Content Types. You’ll see pages and posts already defined. But you can create new ones \u2014 Projects, Products, Team Members \u2014 with custom fields, slugs, and URL patterns.<\/p>\n

The catch? These are stored in the database, not as code. For an experienced practitioner, that’s a red flag. In most production workflows, you want content type definitions in version control, not click-ops. EmDash currently offers no code-first configuration for schemas. You define types through the UI, and they live in D1 (or SQLite locally). That means migrating a site requires either exporting the database or manually recreating types. The team has hinted at code-based schema definitions, but they’re not here yet.<\/p>\n

Security That’s Not a Plugin<\/h2>\n

The headline feature is plugin sandboxing via dynamic workers. If you’re on Cloudflare’s paid plan ($5\/month), every plugin runs in its own V8 isolate. It cannot access your database, file system, or network unless you explicitly declare capabilities in a manifest.<\/p>\n

What That Means for Your Workflow<\/h3>\n

You write plugins as functions with a definePlugin<\/code>codecodecodecode call. You specify capabilities: read content<\/code>codecodecodecode, send email<\/code>codecodecodecode, read media<\/code>codecodecodecode. The runtime enforces these boundaries. A compromised plugin cannot create an admin user, read password hashes, or exfiltrate data. This isn’t a policy \u2014 it’s architectural enforcement via V8 isolates, Linux namespaces, and seccomp filters.<\/p>\n

But here’s the non-obvious part: on the free Cloudflare tier, plugins run in-process. No sandbox. Self-host on Node.js, same story. The feature that justifies EmDash’s existence requires Cloudflare’s paid runtime. The code is MIT-licensed, but the security model is vendor-locked.<\/p>\n

AI Integration That’s Not an Add-On<\/h2>\n

EmDash ships with a built-in MCP server and agent skills files. This is where it diverges most sharply from WordPress.<\/p>\n

The MCP Server<\/h3>\n

Model Context Protocol (MCP) is Anthropic’s standard for AI agent<\/a> communication. EmDash’s MCP server lets Claude, Cursor, or GitHub Copilot connect directly to your CMS. Agents can create content types, migrate themes, update content, and manage plugins \u2014 all through natural language.<\/p>\n

The agent skills files are structured documentation that tells an AI<\/a> exactly how to operate the CMS. No custom prompting needed. This is designed for the world where vibe coding or agent-driven development is the norm. You can say “Build me a new custom content type for testimonials with fields for company name and quote” and the agent handles it.<\/p>\n

Portable Text<\/h3>\n

Content is stored as structured JSON, not HTML. Portable text, the same format Sanity pioneered, renders to web, mobile, email, or API without markup parsing. For an experienced developer, this means you can reuse content across frontends without scraping HTML. WordPress stores content as HTML in the post_content<\/code>codecodecodecode column. EmDash stores it as structured blocks. Migration tools convert WXR exports to portable text, but custom blocks or layouts require manual porting.<\/p>\n

The Real Cost Question<\/h2>\n

EmDash is serverless. You pay per request, per CPU millisecond, per database read, per storage operation. WordPress hosting is a flat monthly fee. EmDash’s paid plan starts at $5\/month with 10 million requests. After that, $0.30 per additional million, plus CPU time, D1 reads, R2 operations, and KV lookups.<\/p>\n

The Hidden Metering<\/h3>\n

One page view can hit five billing meters simultaneously: Workers (compute), D1 (database reads), R2 (media storage), KV (session state), and potentially Workers AI. Predict your monthly bill as a small business owner. You can’t. Cloudflare doesn’t offer a global spending cap. You can set CPU time limits per request and WAF rate limiting, but a distributed bot attack from thousands of IPs bypasses per-IP limits.<\/p>\n

For an experienced practitioner, this means EmDash is cheap for low-traffic sites and unpredictable for anything viral. A blog post hitting Hacker News could cost you more than your hosting bill. Compare that to WordPress: your server might crash under load, but your bill stays the same.<\/p>\n

Migration Is a Content-Only Affair<\/h2>\n

EmDash includes a WordPress migration tool. It imports posts, pages, media, and custom post types via WXR export. That’s it. No plugins, no themes, no WooCommerce products, no membership systems, no SEO configurations. All of that, you rebuild.<\/p>\n

The Portable Text Hiccup<\/h3>\n

WordPress stores content as HTML. EmDash uses portable text. Migration converts block-level content, but custom HTML, shortcodes, or page-builder markup may not survive. For any site with Elementor, Divi, or custom blocks, migration is a rewrite, not a move.<\/p>\n

The team provides an AI-assisted porting guide. Feed your WordPress theme files to an MCP agent, and it generates Astro-compatible templates. That works for simple themes. For anything with custom post types, advanced fields, or complex logic, you’re building from scratch.<\/p>\n

The Ecosystem Challenge<\/h2>\n

WordPress has 60,000 plugins, 12,000 themes, and millions of developers. EmDash launched with zero third-party plugins. The sandbox model means plugins are isolated, but isolation doesn’t create features. Every plugin you need \u2014 e-commerce, forms, SEO, caching \u2014 must be built or ported.<\/p>\n

The counter-strategy is AI. The MCP server and agent skills let developers generate plugins programmatically. The MIT license removes GPL friction for commercial developers. But signals don’t ship features. A business that needs WooCommerce, Yoast SEO, and Gravity Forms can install WordPress plugins in an afternoon. On EmDash, that’s weeks of custom development \u2014 assuming the functionality exists yet.<\/p>\n

For an experienced practitioner, the bet is that AI-generated plugins will close the gap faster than traditional ecosystem growth. That’s plausible, but unproven. Ghost launched a decade ago with better technology than WordPress and has 0.1% market share. Ecosystem is not architecture.<\/p>\n

Where the General Advice Fails<\/h2>\n

The common advice is to wait for v1.0, a real ecosystem, and predictable billing. That’s safe. But it misses the point for greenfield projects where security and modern tooling matter more than legacy compatibility.<\/p>\n

If you’re building a content site in TypeScript, security is a primary concern, and you can manage serverless costs with monitoring, EmDash is worth a serious look today. The architecture is right. The sandbox model solves a real problem. The AI integration isn’t an afterthought.<\/p>\n

But if you need e-commerce, a membership system, or any functionality beyond basic content management, WordPress still wins by default. Not because it’s better, but because its ecosystem has no substitute yet.<\/p>\n","protected":false},"excerpt":{"rendered":"

You’ve installed EmDash. You’ve clicked through the wizard, set your passkey, and landed on the admin. It looks like WordPress. That’s the point. But the surface familiarity hides decisions that change how you build, deploy, and maintain a site. Here’s what matters beyond the first impression. The Dashboard Is a Trap \u2014 But a Useful […]<\/p>\n","protected":false},"author":7,"featured_media":98616,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/97960.png","fifu_image_alt":"EmDash CMS Dashboard: What the Non-Obvious Design Choices Actually Mean","footnotes":""},"categories":[31],"tags":[],"class_list":["post-97960","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/97960.png","fifu_image_alt":"EmDash CMS Dashboard: What the Non-Obvious Design Choices Actually Mean","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/97960","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=97960"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/97960\/revisions"}],"predecessor-version":[{"id":98499,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/97960\/revisions\/98499"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/98616"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=97960"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=97960"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=97960"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}