CMS 13 Is Out, and It's Worth the Attention
CMS 13 has finally hit its official release. The 13.0.0 family of packages is out, ready to be explored, tested, and for some teams, dropped into an ongoing migration.
Most of the discussion I see focuses on feature comparisons or migration readiness. Those are fair questions, but they miss the more interesting story. This is a platform being deliberately shaped for AI-first workflows. What's already shipped gives you a meaningful foundation today. What's coming next will make the gap between CMS 13 and CMS 12 increasingly hard to bridge from the other side.
If your organization is serious about AI adoption, not just experimenting with it, understanding where CMS 13 is heading matters right now.
What's Already There: The AI Angle
I'm going to skip the general feature tour here. If you want a full list, the release notes have it. What I want to focus on is the subset of things that actually move the needle for AI adoption.
Graph as the RAG Backbone for Opal
This one tends to get undersold. Optimizely Graph isn't just a content delivery API. In CMS 13, it's the retrieval layer that powers Opal. When Opal needs to reason about your content, answer questions about it, or generate something based on it, Graph is how it gets that context. That's Retrieval Augmented Generation (RAG) built into the platform.
For teams that have invested in properly structuring their content in Graph, this pays off immediately. Well-modelled, queryable content means Opal can work with it intelligently. Poorly structured content means you'll hit the limits of what AI can do with it quickly. If you're evaluating CMS 13 from an AI perspective, your Graph schema quality matters more than ever.
Ready-to-Use Opal Agents
A set of out-of-the-box Opal agents ships with CMS 13. These aren't demos or proofs of concept. They're practical, repeatable workflows for common editorial tasks: translation, content summarization, SEO suggestions, and more, all available and usable today.
This matters because it lowers the barrier to actual AI adoption inside teams. You don't need to build custom tools before editors can start working with AI. The starting point is already useful and extendable if you need more. I wrote a full guide on building your own Opal tools here if you want to go further.
Visual Builder and Composable Content
Visual Builder arrives in CMS 13 alongside the new Content Manager. The shift from pages to composable content pieces isn't just a UX change. It's an architectural one with real implications for AI.
Composable, structured content is content that AI can actually work with. Monolithic page blobs are hard to reason about, hard to generate reliably, and hard to validate. Discrete components with clear types and relationships are much more tractable. Whether you're feeding content into an LLM, generating it with one, or building search experiences on top of it, structure is what makes AI useful rather than unpredictable.
DAM and CMP: Closing the Content Loop
Digital Asset Management is part of Optimizely CMP, so this is specifically relevant for CMP customers. In CMS 13, your assets now have a more direct relationship with your CMS content, which helps with AI-driven workflows that need to work with copy and media together.
The bigger AI story here is what the tighter CMP and CMS integration enables. CMP is where content strategy lives: briefs, campaigns, calendars, approval flows. CMS is where content gets published. Bringing them closer together means AI can participate across the full lifecycle, generating content based on a brief in CMP, moving it through review, and publishing it in CMS. Right now that workflow has manual handoffs that break the chain. As the integration matures from manual to automated, that chain gets shorter and AI can operate more fluidly across it.
If you're thinking about AI adoption as a content operations story and not just an authoring tool story, this integration matters.
Opal Chat
Opal Chat was available in CMS 12 as well, so this isn't a new capability. But it's fully there in CMS 13 and worth calling out. Having a conversational AI interface inside the CMS changes the daily workflow for editors. Instead of switching to an external tool, the assistant is part of the authoring experience. Small difference in theory, noticeable difference in practice.
What's Coming Next
A recent Optimizely webinar laid out the near-term roadmap. Here's what stands out from an AI perspective:
CMS MCP Server: The One to Watch
CMS MCP (Model Context Protocol) will give AI systems direct access to Optimizely tools and content. Not just Opal, but any MCP-compatible client. This is the feature I'm most excited about and the one I think will matter most in the long run.
Model Context Protocol is becoming the standard way for AI systems to connect to external tools and data sources. Once Optimizely ships an MCP server for CMS 13, your CMS becomes a first-class participant in any AI workflow you build: Claude Code, custom agents, external orchestration systems, whatever you're working with. You're no longer limited to what Opal exposes in its UI. Any AI system that speaks MCP can read, write, and orchestrate content.
I already have a list of things I want to build the moment I can get my hands on this. The gap between CMS 12 and CMS 13 for AI-first development is significant today. With MCP, it becomes a different conversation entirely.
Opal Agent for AI-Driven Content Creation
Optimizely announced a dedicated agent for AI-driven content creation. This goes beyond chat-based assistance. It's a structured workflow where AI participates in the authoring process itself: generating drafts, suggesting variations, validating against content guidelines, and fitting output into your content model.
For editorial teams trying to scale content production without scaling headcount, this is directly relevant. It's not a chatbot you ask questions. It's a collaborator integrated into the authoring flow.
Claude Skills for CMS 12 to CMS 13 Migration
This one deserves a better headline than "migration improvements."
Optimizely is shipping Claude AI skills specifically designed to assist with the CMS 12 to CMS 13 migration, including migrating from Optimizely Search and Navigation to Optimizely Graph. Think about what that means in practice. Upgrades between major versions have always been one of the more painful things in CMS work: hours of documentation, manual review, edge case hunting.
What if instead you could describe your current setup to Claude and get a concrete migration path back? What if the skill could analyze your configuration and tell you what needs to change and why? That's the direction this is pointing.
Migrations have always been a reason teams stayed on older versions longer than they should. If AI can meaningfully reduce that friction, it changes the calculus around staying current. For me personally, this is the second most exciting thing on the roadmap, right behind MCP.
Final Thoughts
CMS 13 is a platform being built with a clear direction: AI as a first-class participant in how content is created, managed, delivered, and orchestrated.
What's already there, Graph as a RAG backbone, ready-to-use agents, composable content, gives you a meaningful foundation today. What's coming, MCP, the content creation agent, AI-assisted migration, is where the platform moves well beyond what CMS 12 can offer even with add-ons.
If your organization is planning to seriously adopt AI in your content workflows, the question isn't really whether to move to CMS 13. It's when, and how to sequence it.
The platform has picked a direction. It's the right one.