What changes when your CMS stops dictating how and what you build
Blog post from Sanity
An enterprise product manager found that AI agents could not reliably fix layout issues in Adobe Experience Manager (AEM) because they had to rely on rendered pages or complex underlying repositories rather than directly access and verify CMS components, while a similar workflow worked with a frontend and content system the team controlled. Other examples describe manual content updates at a retailer and schema-management difficulties at Tata Digital, illustrating how teams can develop workarounds when content is organized around pages or managed through platform-specific processes. The text contrasts AEM’s page-centered origins with Sanity’s approach of modeling content as structured entities, keeping models and functions in code, and making content available to agents through MCP. It also argues that the cost of running AEM includes specialist staffing and delays, not just licensing, and suggests that organizations planning a migration should decide whether to preserve page-first structures or reshape content so it can be reused and accessed directly by agents.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 1 | 9,757 | 959 | 203 | -18% |
| Sanity Context | 1 | 1 | 1 | 1 | -91% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.