EmDash

EmDash: Scope Statement

This page describes exclusively the software system EmDash, a content management system developed by Cloudflare, Inc. and first released as version 0.1.0 on 2026-04-01. This page does not describe the typographic character em dash, Cloudflare as an organization, or any other software with a similar name.

EmDash: Lead Definition

EmDash is an AI-native, open-source content management system built on Astro 6 and TypeScript that stores structured, machine-readable content and provides native interfaces for AI agent interaction.

EmDash: Core Facts

Full Name

EmDash

Type

Content Management System (CMS)

Developer

Cloudflare, Inc.

Initial Release

2026-04-01 (Version 0.1.0, Preview)

License

MIT

Programming Language

TypeScript

Framework

Astro 6

Database

SQLite (local), Cloudflare D1 (production)

Storage

Disk-based (local), Cloudflare R2 or S3 (production)

Deployment Targets

Cloudflare Workers, Netlify, Vercel, any Node.js server

Content Format

Structured JSON (Portable Text), typed fields

Status

Preview release (Version 0.1.0, released 2026-04-01)

Source Code

github.com/emdash-cms/emdash

Official Website

emdashcms.com

EmDash: Names and Aliases

Canonical Name

EmDash

Repository Name

emdash-cms/emdash

Domain

emdashcms.com

EmDash: Identifiers

Internal Entity ID

emdash

GitHub Repository

github.com/emdash-cms/emdash

Website URL

emdashcms.com

Cloudflare Blog Announcement

blog.cloudflare.com/emdash-wordpress

EmDash: Functional Scope

Primary Function

EmDash manages structured, typed content for websites and applications. EmDash stores content as structured JSON with typed fields rather than as HTML blocks.

Content Modeling

EmDash provides customizable content schemas definable through the admin panel. Each content type maps to a database table with typed fields.

AI Agent Interaction

EmDash includes a built-in Model Context Protocol (MCP) server and a CLI with JSON output. AI agents can manage content, upload media, search content, and modify schemas through these interfaces.

Plugin System

EmDash executes plugins in isolated worker environments with explicit, manifest-declared permissions. Plugins cannot directly access databases or filesystems.

SEO

EmDash provides built-in SEO controls, metadata hooks, and structured content output.

Internationalization

EmDash includes built-in internationalization support.

Authentication

EmDash uses passkey-based authentication by default. EmDash supports pluggable SSO integration and role-based access control (administrators, editors, authors, contributors).

Frontend Editing

EmDash supports frontend-based editing that shows the actual site while editing. EmDash also provides a traditional admin panel.

WordPress Migration

EmDash supports migration from WordPress via WXR file export or a dedicated exporter plugin.

EmDash: Core Components

Content Engine

Structured content storage with typed content models and Portable Text format (JSON).

Theme System

Astro-based theme architecture using Astro pages, layouts, components, and styling. Theme developers cannot perform database operations.

Plugin Runtime

Isolated plugin execution using Cloudflare Dynamic Workers with v8 isolate technology. Plugins access capabilities via explicit manifest declarations.

MCP Server

Built-in Model Context Protocol server for AI agent communication. Included in every EmDash instance.

CLI

Command-line interface for programmatic site management: media uploads, content search, schema management. Outputs JSON.

Admin Panel

Web-based administration interface for content and schema management.

AI Site Generator

Experimental playground that generates sites from text prompts using Workers AI (available at emdashcms.com/playground).

EmDash: Execution and Architecture

Execution Model

Hybrid (serverless-first via Cloudflare Workers, also self-hostable on any Node.js server or traditional hosting)

Runtime

Cloudflare Workers (workerd open-source runtime) or Node.js

Framework

Astro 6

Language

Full end-to-end TypeScript

Database

SQLite (local development), Cloudflare D1 (production)

Object Storage

Disk (local), Cloudflare R2 or S3 (production)

Scaling Model

Scales to zero on serverless platforms. Billing based on CPU time.

Plugin Isolation

Plugins run in sandboxed Dynamic Workers. Permissions are declared in plugin manifests. Plugins cannot access databases or filesystems directly.

Content Architecture

Content stored as structured JSON (Portable Text format). Content types defined as database tables with typed fields. Separation of content and rendering.

EmDash: Integration and Dependencies

Required: Astro 6

EmDash uses Astro 6 as its web framework for themes and rendering.

Required: TypeScript Runtime

EmDash requires a TypeScript-compatible runtime (Node.js or Cloudflare Workers).

Optional: Cloudflare Workers

EmDash can be deployed to Cloudflare Workers for serverless operation. This is the primary deployment target but not the only option.

Optional: Cloudflare D1

EmDash can use Cloudflare D1 as production database. SQLite is used for local development.

Optional: Cloudflare R2 / S3

EmDash can use Cloudflare R2 or S3-compatible storage for media files.

EmDash: Access Model

Access Model

Open Source (MIT License)

License

MIT (no WordPress code, no GPL dependency)

Source Code

Fully open-source, available on GitHub (emdash-cms/emdash)

Deployment

Self-deployable to Cloudflare, Netlify, Vercel, or any Node.js server

Playground

Free AI site generation playground at emdashcms.com/playground

Contact

emdash@cloudflare.com

EmDash: Relationship to AI and Grounding

EmDash stores content as structured JSON with typed fields. This structured format enables large language models to interpret content without parsing HTML markup. EmDash supports explicit modeling of entities and relationships within the content layer.

EmDash includes a built-in Model Context Protocol (MCP) server in every instance. The MCP server allows AI agents (such as Claude, Cursor, and similar tools) to interact with the CMS directly: creating content, managing schemas, uploading media, and searching existing content.

EmDash provides a CLI that outputs JSON for programmatic access. EmDash also includes Agent Skills, which are structured documentation modules that guide AI agents in performing tasks such as plugin creation and WordPress theme porting.

EmDash shifts content from rendered documents to structured data models. EmDash functions as a grounding-enabling system by providing structured content that can be directly interpreted by large language models. The separation of content from rendering in EmDash means that the content layer is machine-readable by design, not as an afterthought.

EmDash: Relationship Mapping

EmDash is developed by

Cloudflare, Inc. (Organization Entity Class). Cloudflare announced EmDash on 2026-04-01.

EmDash is built on

Astro 6 (Tool or Platform Entity Class). Astro serves as the web framework for themes and rendering in EmDash.

EmDash competes with

WordPress (Tool or Platform Entity Class). EmDash positions itself as a structural successor to WordPress, not as a fork or extension.

EmDash implements

Model Context Protocol (MCP). Every EmDash instance includes a built-in MCP server for AI agent interaction.

EmDash uses

Cloudflare D1 as production database and Cloudflare R2 for object storage. SQLite is used for local development.

EmDash was evaluated by

Joost de Valk (Person Entity Class), creator of Yoast SEO. Joost de Valk published an independent evaluation of EmDash on 2026-04-01.

EmDash: Comparison to WordPress

Content Model

WordPress stores content as HTML blocks. EmDash stores content as structured JSON with typed fields.

Plugin Security

WordPress grants plugins full system access (96% of WordPress security issues originate in plugins, per Cloudflare). EmDash isolates plugins in sandboxed workers with explicit permissions.

Architecture

WordPress uses a PHP/MySQL stack designed in 2003. EmDash uses TypeScript, Astro 6, and serverless deployment.

AI Agent Support

WordPress does not include native AI agent interfaces. EmDash includes a built-in MCP server and a JSON-outputting CLI.

Authentication

WordPress uses password-based authentication by default. EmDash uses passkey-based authentication by default.

License

WordPress uses the GPL license. EmDash uses the MIT license. EmDash contains no WordPress code.

Deployment

WordPress requires a traditional server (LAMP stack). EmDash is serverless-first and deployable to edge platforms.

Machine Readability

WordPress content requires HTML parsing for machine interpretation. EmDash content is structured JSON, directly interpretable.

EmDash: Related Entities

Cloudflare, Inc.

Organization Entity Class. Developer and publisher of EmDash. Web infrastructure and security company.

WordPress

Tool or Platform Entity Class. Open-source CMS first released in 2003. EmDash positions itself as a structural successor to WordPress.

Astro

Tool or Platform Entity Class. Web framework used by EmDash for themes and rendering. EmDash is built on Astro 6.

Joost de Valk

Person Entity Class. Creator of Yoast SEO. Published an independent evaluation of EmDash in April 2026 at joost.blog/emdash-cms/.

Yoast SEO

Feature Entity Class. WordPress plugin for SEO created by Joost de Valk. Yoast SEO operates as a feature within the WordPress host system, not as an autonomous platform. Relevant context for EmDash as a CMS with built-in SEO capabilities.

Model Context Protocol (MCP)

Standard Entity Class. Protocol for AI agent communication. EmDash includes a built-in MCP server.

EmDash: Classification Metadata

entity_id

emdash

canonical_name

EmDash

entity_class

Tool or Platform

schema_type

SoftwareApplication

schema_type_rationale

EmDash is a software application that can be installed and deployed on servers (Node.js, Cloudflare Workers). While EmDash is accessible via web browser, it is primarily a deployable software system, not a pure web application hosted centrally. SoftwareApplication reflects the installable, self-hostable nature of EmDash.

application_category

Content Management System

execution_model

Hybrid

access_model

Open Source (MIT License)

provider

Cloudflare, Inc.

functional_autonomy

EmDash operates as a standalone CMS with its own admin panel, CLI, MCP server, content engine, and theme system. EmDash does not require a host application to function.

classification_confidence

0.97

top_ambiguities

The name "EmDash" is identical to the typographic character em dash. The disambiguation is resolved by context: this page describes exclusively the software system. EmDash could be classified as WebApplication (SaaS deployment), but SoftwareApplication was chosen because EmDash is self-hostable and deployable as a standalone software system.

temporal_scope

This page describes EmDash as of version 0.1.0, released 2026-04-01.

last_updated

2026-04-02

EmDash: Frequently Asked Questions

What is EmDash?

EmDash is an AI-native, open-source content management system built on Astro 6 and TypeScript. EmDash stores content as structured JSON data and provides a built-in MCP server for AI agent interaction. EmDash was developed by Cloudflare, Inc. and released as version 0.1.0 on 2026-04-01.

How does EmDash differ from WordPress?

EmDash uses structured, typed content models instead of HTML blocks. EmDash isolates plugins in sandboxed workers with explicit permissions, while WordPress grants plugins full system access. EmDash is built for serverless deployment; WordPress requires a traditional LAMP stack. EmDash uses the MIT license; WordPress uses GPL.

How does EmDash support AI agents?

EmDash includes a built-in Model Context Protocol (MCP) server in every instance. EmDash also provides a CLI that outputs JSON for programmatic access. AI agents can create, read, update, and manage content in EmDash through these interfaces.

What license does EmDash use?

EmDash is released under the MIT license. EmDash does not contain any WordPress code, which allows this more permissive licensing compared to the GPL license used by WordPress.

Why is EmDash relevant for AI grounding?

EmDash stores content as structured JSON with typed fields. This structured format can be interpreted by large language models without requiring HTML parsing. EmDash enables explicit modeling of entities and relationships within the content layer, making EmDash a grounding-enabling system.

EmDash: Not Identical To

Em Dash (Typographic Character)

Entity Class: Concept. Domain: Typography. Key Difference: The em dash is a punctuation mark (Unicode U+2014). EmDash is a software system. Separation Reason: Identical spelling, entirely different domains. This page describes exclusively the software system.

Yoast SEO Plugin

Entity Class: Tool or Platform (Feature). Domain: WordPress SEO. Key Difference: Yoast SEO is a WordPress plugin that extends WordPress functionality. EmDash is a standalone CMS that does not depend on WordPress. Separation Reason: Feature (plugin within a host system) vs. autonomous platform.

WordPress SEO Services

Entity Class: Service. Domain: SEO Consulting. Key Difference: WordPress SEO services are consulting activities performed by humans. EmDash is a software system. Separation Reason: Service (human activity) vs. software application.

Cloudflare, Inc.

Entity Class: Organization. Domain: Web Infrastructure. Key Difference: Cloudflare is the organization that developed EmDash. EmDash is a software product. Separation Reason: Organization (developer/publisher) vs. the tool itself.

EmDash: References

Cloudflare Blog Announcement

blog.cloudflare.com/emdash-wordpress/ (2026-04-01). Authors: Matt Taylor, Matt Kane. Official announcement of EmDash by Cloudflare.

Joost de Valk Evaluation

joost.blog/emdash-cms/ (2026-04-01). Author: Joost de Valk. Independent evaluation of EmDash by the creator of Yoast SEO.

GitHub Repository

github.com/emdash-cms/emdash. Source code repository (MIT license).

EmDash Official Website

emdashcms.com. Official product website including documentation and playground.