Get the latest!

Four patterns Optimizely practitioners could be getting wrong with Opal agents: inference levels, oversized tool responses, missing output constraints, and no agent response caching.

Andy Blyth

Optimizely CMS 13 is not just another version upgrade—it represents a deliberate shift toward a connected, AI-enabled, and API-driven content platform . Released March 31, 2026, CMS 13 introduces: A Graph-first architecture for content delivery...

Augusto Davalos

I’ve seen this before… The pattern. The rush, the excitement, the scramble to adopt something new before anyone has stopped to ask what problem it actually solves. The first twenty years of my career were in print. Fifteen of those were at one of...

Mark Welland

Scheduled jobs is an integral part of most Optimizely solution but the UI has, in my opinon, always been lacking in usability and features. Earlier this year I did a small tool that tried to give a better overview  and make it easier digging into...

Per Nergård (MVP)

Almost every CMS served website has some concept of dynamic content resolution. A means to serve up related or latest content links while minimising the burden on the content editors. This style of functionality is commonly delivered through...

Mark Stott

Learn what to to with the warning: 'PageReference' is obsolete: 'Use ContentReference instead.'

Tomas Hensrud Gulla

Upgrading an Optimizely (formerly EPiServer) CMS solution has traditionally been a high-risk, resource-intensive endeavor. Transitioning from CMS 11 to modern versions (CMS 12/13) requires a fundamental shift from .NET Framework to .NET Core/8/10,...

Vaibhav

Tired of migration flashbacks? Optimizely CMS 13 is the evolution we’ve earned. Learn why the move to .NET 10 is easier and how AI-first orchestration changes the game

Stuart