Optimizely CMS 13 represents the next generation of the platform, bringing both new functionality and new ways of working.

At its core, the upgrade marks a shift in how content is managed, moving from page-based publishing to more structured and reusable content. This changes both how content is created and how it is used across digital environments.

For organisations planning an upgrade, this is about building the foundation for a more structured and scalable way of working, where content can be managed consistently across channels with greater control and governance.

In Optimizely CMS 13, the focus shifts from treating content as pages to managing content as standalone resources. Content is no longer created primarily for a single destination. Instead, it is structured to be reused across multiple contexts, including websites, apps, internal systems and other digital services.

A product or service description is no longer just a page. It becomes a content resource that can be used across campaigns, search experiences and personalised journeys without duplication.

This shift makes the content model more important than the page structure. Instead of relying primarily on navigation and page trees, content types and the relationships between content become central to how content delivers value over time. Optimizely Graph acts as a semantic layer, making content searchable, connected and reusable across channels.

For editorial teams, Optimizely CMS 13 introduces a clear shift in how content work gets done. With the introduction of Visual Builder, editors can work more directly in a visual environment, often reducing the time from idea to publication.

Built-in AI capabilities through Opal allow the platform to suggest, refine and improve content directly within the editorial workflow. This can include alternative headlines, structural recommendations and optimisation suggestions.

As a result, editorial work increasingly becomes about orchestrating, quality-assuring and combining content rather than creating everything from scratch. As content becomes more modular, the content model and its structure play a much bigger role in day-to-day operations. This places greater importance on clearly defining content types and establishing how they should be used over time.

It also creates the foundation for a more continuous improvement cycle, where content can be tested, measured and refined based on performance across channels.

For development and IT teams, upgrading to Optimizely CMS 13 represents a significant technical shift.

At the core is a more API-driven architecture built on decoupled components. Content is managed and distributed through services such as Optimizely Graph, enabling the platform to move beyond traditional web publishing and operate as a central content hub for other systems and digital touchpoints.

Optimizely CMS 13 is a more flexible platform than previous versions. APIs, structured data and modular components make this possible. It also means the upgrade should be approached as a broader technical and structural transformation rather than a standalone technical project.

In practice, content models, integrations and delivery flows need to be reviewed in relation to how content is used today and how it is expected to support more channels and interfaces going forward.

A key part of the upgrade process is assessing the current implementation from three perspectives:

• What can be reused in the new architecture
• What needs to be restructured to support a more modular content model
• What can be simplified when content is no longer tied to pages

At the same time, development increasingly moves towards APIs, structured data and decoupled components. This creates greater long-term flexibility, but it also reinforces the need to plan the upgrade as a coordinated technical and structural initiative.

What is the biggest difference in CMS 13 compared to earlier versions?
The shift lies in how content is modelled and used. The focus moves from pages to structured content that can be reused across multiple channels and systems.

Do you still work with pages in CMS 13?
Yes, but pages become more of a presentation layer for content rather than the primary structure for creating and organising it.

What is Optimizely Graph?
It is a semantic layer that makes content searchable and available via APIs, enabling reuse across multiple digital channels.

How are editorial teams affected?
Work becomes more modular, with a stronger focus on combining, governing and quality-assuring content rather than creating everything from scratch.

Is CMS 13 only a technical upgrade?
No. It is both a technical and organisational shift that affects content models, ways of working and architecture.

What does an API-based architecture mean in practice?
It means content is not only delivered to a website, but can be consumed by multiple systems and interfaces through APIs.

Should we talk about Optimizely?
Yes — in most cases it’s appropriate to explicitly position Optimizely when discussing CMS 13, since the platform, Graph and ecosystem are tightly integrated and part of the value proposition.