emdash-developer.html

emdash CMS developer building on the Astro-first, capability-bounded successor to WordPress

emdash is the open-source TypeScript CMS shipped by Cloudflare in early 2026 — Astro frontend, Cloudflare Workers backend, sandboxed plugin permissions. The first CMS that takes the WordPress-plugin-attack-surface problem seriously.

BOOK A 30-MIN CALL

Category: Headless CMS Hires from: Seahawk Media (12,000+ sites shipped) Engagement: 4 weeks minimum, project or retainer

What emdash CMS actually is — and where it fits

emdash is the open-source CMS shipped by Cloudflare in April 2026 (v0.1.0 preview, MIT licence). Built on Astro and TypeScript, deploys to Cloudflare Workers as the primary target with Node.js as the alternative. Three architectural differentiators: (1) capability-bounded plugin model — plugins declare permissions up-front instead of WordPress's all-access default, (2) per-post-type dedicated tables instead of a generic posts table, (3) AI-first integration with a built-in MCP server and JSON CLI so AI agents are first-class builders, not afterthoughts. Currently early — v0.1.0 preview as of April 2026 — but the architectural choices are correct.

Best fit for these briefs

  • Teams already on the Cloudflare Workers + Astro stack who want a CMS that fits the deployment topology natively
  • Security-conscious organisations tired of the WordPress plugin attack surface and looking for a sandboxed-plugin alternative
  • AI-native content workflows where the CMS needs to expose itself cleanly to MCP / agent tooling, not bolt it on later
  • Greenfield projects where adopting a v0.x CMS is acceptable in exchange for being on the right architecture from day one

Three things most emdash CMS engagements get wrong

It is v0.1.0 — production deployments are early-adopter risk

April 2026 release means breaking changes between minor versions are likely for the next 12-18 months. Use it where you can absorb that, avoid it for mission-critical sites that need a stable platform until at least v1.0.

TinyMCE-based editor is not a block editor

Maciek Palmowski's review flagged this — emdash chose classic TinyMCE rather than block-based editing. For content teams used to Gutenberg or Sanity Studio, the editorial UX feels like a step back. Whether that's pragmatic or regressive depends on your team.

Plugin ecosystem barely exists yet

v0.1.0 means the third-party plugin marketplace is empty. Common patterns (forms, SEO, sitemap, multi-language) need first-party implementation or custom plugin work. Budget engineering time accordingly until the ecosystem matures.

What you get when you hire me for emdash CMS

One senior on every engagement

I am the senior on the call, the senior on the architecture review, and the senior who answers when something breaks at 11pm. The build is delivered with senior engineers from Seahawk Media under my direction; the kickoff and the handover are with me directly.

Real emdash CMS experience, not "we read the docs once"

The emdash CMS space is full of agencies that bolted the platform onto a generic offer. The questions a senior emdash CMS developer answers — content modelling, schema migration, performance, observability, multi-environment workflows — are the questions you actually need answered, and that is where the engagement earns its fee.

Modern stack pairing

Most emdash CMS engagements pair the platform with Next.js, Astro, or a modern frontend stack. I have shipped both sides of that pairing across 50+ projects. The integration patterns, the deployment topology, the SEO transport on migrations — all of it has been done before, and you get the lessons rather than paying for them in your project.

Engagement shape, in practice

I take on a small number of emdash CMS engagements at any given time. Two shapes that fit best:

Project — 4 to 12 weeks, fixed-price. Clear scope (a content migration, a Studio customisation, a performance audit, a build from scratch). Discovery week first, then a fixed-price quote. Most projects land in the 12,000-60,000 USD range.

Retainer — 8 hours per week, monthly. Ongoing emdash CMS engineering support after launch. Schema evolution, new feature work, integration help with adjacent stacks. Typical retainer 6,400-12,800 USD/month depending on complexity.

Booking sequence: 30-minute call, you describe the brief, I tell you which shape fits and the price range. No sales deck, no qualification screen. If I am not the right person, I will tell you on the call.

Related on this site

When you are ready

Book a 30-minute call. By the end of it you will know whether emdash CMS is the right pick for your brief, what the realistic scope is, and a price range that fits your budget. If emdash CMS is not the right answer, I will tell you and recommend the alternative.