Agents need somewhere to live. And once content becomes data, the CMS that holds it becomes strategic.

Agents need somewhere to live.

For years, organizations chose a CMS the traditional way: based on editorial usability, templates, components, and how fast teams could publish pages. That made sense. In the SaaS era, most of the perceived value lived in the application layer: the interface, the dashboard, the workflows defined by the vendor.

But that logic is shifting.

Scott Brinker describes this clearly [2]: as AI makes it easier to build custom apps and agents, the durable value in martech is moving to the layers underneath: data, governance, semantics, context, and orchestration. That’s why a CRM decision is no longer just a CRM decision. It’s an AI infrastructure decision.

The same shift is now happening for CMS.

Content Is No Longer Content. It’s Data.

The more interesting insight comes from Stacks on a Plane [3].

Brinker outlines a universal data layer composed of five types of data: customer data, company data, content data, code data, and control data. What stands out is that content is explicitly part of that core, not as an afterthought, but as a first-class data type.

And then comes the real shift:

Content is no longer something you just store and retrieve.
It becomes something systems can reason over.

When brand guidelines, assets, metadata, and performance data live on the same plane as everything else, content stops being static. It becomes operational.

And that changes everything for CMS platforms.

Because once content is treated as data, a CMS is no longer just a publishing tool. It becomes part of the data infrastructure.

And that likely makes it more important, not less.

From Publishing Tool to Content Infrastructure

In this new model, a CMS is no longer primarily about building pages.

It becomes about:

• modeling content
• structuring data
• managing metadata
• tracking revisions
• governing workflows
• controlling permissions
• exposing everything via APIs

In other words, it becomes a system of context for content.

That aligns almost perfectly with Brinker’s idea of domain-specific platforms evolving into “systems of context” that sit on top of the data layer and make it usable for agents and applications.

And that is exactly what agents need.

Agents Don’t Need Pages. They Need Governed Context.

An agent doesn’t care about a webpage.

It cares about:

• what is approved vs draft
• which version is authoritative
• what applies to which market or segment
• what disclaimers are required
• what language version is valid
• who is allowed to change what

Without that, you don’t have an AI system.
You have automated chaos.

This is where the concept of control data becomes critical: policies, permissions, business rules, and guardrails that ensure AI operates safely and consistently.

For content-driven organizations, that governance layer is exactly what a mature CMS is supposed to provide.

Why Drupal Fits This Shift

This is where Drupal becomes highly relevant.

Not because it is “a good CMS,” but because of how it models and governs content:

• structured content types and entities
• revisioning and version control
• workflow states and transitions
• role-based permissions
• multilingual content management
• API-first architecture

These are not just editorial features.
They are infrastructure capabilities.

They allow content to exist as governed, queryable, structured data that both humans and agents can safely use.

In Brinker’s model, there is a layer between raw data and agents where context is assembled for a specific use case or domain.

For content, Drupal can evolve into exactly that layer: a system that delivers content-context, not just content.

The CMS Decision Changes

This fundamentally changes how organizations should evaluate a CMS.

The question is no longer: “Can our editors work efficiently?”

The real question becomes: “Can our agents operate safely and effectively on this platform?”

• Can it expose structured content via APIs?
• Can it enforce workflows and approvals?
• Can it manage versions and translations?
• Can it provide semantic clarity and metadata?
• Can it act as a governed source of truth?

You are no longer buying an interface.

You are choosing infrastructure.

CMS Becomes More Strategic in the AI Era

There’s a common assumption that AI will make CMS platforms less relevant.

The opposite may be true.

Because if everything becomes data, then:

• content becomes data
• workflows become data
• prompts become data
• governance becomes data

And CMS platforms sit right in the middle of that transformation.

As Brinker puts it, martech no longer just sits on data. It is data.

That means the systems that structure, govern, and expose that data become critical.

Final Thought

So yes, just like CRM, the CMS decision is becoming an AI infrastructure decision.

Not because websites disappear.

But because agents appear.

And those agents need somewhere to live.

For content-driven organizations, that place is increasingly the content layer.

And that makes Drupal not just a CMS.

But a foundation for AI-native digital experiences.