Get the latest!

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

Tomas Hensrud Gulla
workspace_premium +6

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
workspace_premium +1

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
+5

How assumptions can lead to mysterious issues.

Damian Smutek
+3

OptiPowerTools.Hangfire 2.0 adds Optimizely CMS 13 / .NET 10 support and ships ready-to-run sample jobs to shorten Hangfire setup on Optimizely projects.

Stanisław Szołkowski
workspace_premium +6

When I released OptiPowerTools.Hangfire back in March, it targeted Optimizely CMS 12. With CMS 13 now out and running on .NET 10, it was time to bring the package along. Version 2.0.0 adds full CMS 13 support, and I also shipped 1.0.1 on the CMS 1...

Stanisław Szołkowski
workspace_premium +6

This post walks through how to wire together Optimizely CMS 12, Keycloak and .NET Aspire to give you a single local development environment that handles both interactive browser login and machine-to-machine (M2M) API calls from the same ASP.NET Co...

Andreas Ylivainio
workspace_premium +2

Introduction With the release if Optimizely PaaS CMS 13, there is a new way to create UI editor descriptors to allow to custom UI with managing a property. These have been one of the reasons partners can make the jobs of editors much easier by...

Mark Hall