Get the latest!

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService Configuration. However those setting changes require a restart (or even worse, a re-deployment), which is no...

Quan Mai

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or two. It creates value, but it’s inconsistent, difficult to scale, and almost impossible to govern i...

Augusto Davalos

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world that has already moved on. If your team is still running on CMS 11 or CMS 12, this is not a nudge. It...

Muhammad Talha

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises running Optimizely CMS 12 or 13, Digital Asset Management (DAM) is no longer optional; it is the strategic...

Vaibhav

Custom IValidate validators in Optimizely CMS 13 are no longer auto-discovered. They must be registered explicitly when upgrading from CMS 12.

Tomas Hensrud Gulla

Upgrading from Optimizely CMS 12 to CMS 13 alongside moving the runtime from .NET 8.0 to .NET 10.0 is far more than a routine version upgrade. It is an opportunity to rethink how content is structured, queried, and delivered across modern digital...

Sanjay Kumar