Introducing Emdash CMS for Tedix

We're dogfooding our own platform — migrating the Tedix blog to Emdash, the open-source Astro-native CMS built for the AI era. Here's why and how.

Adriana Carmona
Updated May 9, 2026

Today we're announcing that the Tedix blog is now powered by Emdash CMS — the same content management system we offer to every organization on our platform. This isn't just a technology migration; it's proof that our stack works end-to-end.

Why Emdash?

Emdash is an open-source, Astro-native CMS built by Cloudflare. It stores content as Portable Text — structured JSON that's far richer than markdown. Every block, every inline annotation, every embed is a typed object that AI agents can read, write, and transform programmatically.

For Tedix, this means our digital workers (tedis) can manage content through 43 MCP tools — creating posts, managing taxonomies, uploading media, and configuring schemas without ever touching a browser.

The Architecture

Each organization on Tedix gets an isolated CMS instance running as a Workers for Platforms User Worker. Your CMS lives at {slug}.cms.tedix.dev with its own D1 database and R2 media storage. The same Emdash bundle runs everywhere — per-org bindings provide the isolation.

Vibe-Coding Themes with CMS Studio

CMS Studio is our MCP-first vibe-coding environment for Emdash themes. Connect any MCP client — Claude Code, ChatGPT, or your own tedi — and describe the theme you want. The AI agent writes Astro components, Tailwind CSS, and page templates while you watch the preview update in real-time. When you're happy, one command deploys to your live CMS. Version history and rollback are built in.

What's Next

We're building custom Emdash plugins for AEO scoring, citation tracking, and view analytics — all vibe-coded through CMS Studio. The Tedix blog becomes the proving ground for every feature we ship to customers.

Tagged with