Optimizely (Episerver)

[Series: Headless Site on Optimizely Graph] Exploring interesting ways we can query the content

Look up in the sky! It's a bird! No, wait - it's Optimizely Graph! This is part 2 in the blog post series where we explore how a fully functioning headless site can be build in .NET core using Optimizely Graph, and in this post we'll see how Optimizely Graph is both a powerful search & query engine (on par with good old Episerver Find) - but also how it can fully replace the content delivery API.

.NET Development CMS Optimizely (Episerver)Information Retrieval API Building

August 24 2024

New Series: Building a .NET Core headless site on Optimizely Graph and SaaS CMS

Welcome to this new multi-post series where you can follow along as I indulge in yet another crazy experiment: Can we make our beloved Alloy site run as a headless site on top of Optimizely Graph (and SaaS CMS) using a mix of both MVC, Razor Pages and Blazor components - and can we make both the developer and editor experience as we are used to in classic Optimizely/Episerver sites? Let's find out!

CMS .NET Development Optimizely (Episerver)

June 14 2024

Upgrade To Optimizely CMS 12 Issue: List item fields have become Required

There are many funny details to be aware of when upgrading from Episerver CMS 11 to Optimizely CMS 12. One of them that might feel a bit confusing is when your list items start to have all required fields in the UI. Here's how to fix it.

C#Optimizely (Episerver)

June 7 2024

Christmas Countdown: #1 The Grand Finale. Going headless without using your head!

In 2014 the term 'headless cms' was coined - and presented as a cool new 'feature' in the Web CMS industry. And it quickly became a hot buzzword for a few years later. In a few days it's 2024 and we can celebrate that it's been a concept for 10 years. Strangely, I still encounter new implementations that want to go 'headless' based on an almost religious belief that it's the new cool thing.

CMS Optimizely (Episerver)Frontend Development Website Improvements Tech Talk

December 23 2023

Christmas Countdown: #2 We're live! That means we're done, right?

They day you go live with your new website is naturally the culmination of months, sometimes years of work - and it's fine to celebrate. But #2 on this top 12 list of common pitfalls is to think that going live is the completion of the website. It's not. It's the start...

CMS Optimizely (Episerver)Website Improvements Tech Talk

December 22 2023

Christmas Countdown: #3 NIHS - Not Invented Here Syndrome in real life

One of the most common and dreaded diseases in web site development often go undiagnosed and untreated for a long time. But it really should be, cause the effects are scary. Yes, I'm talking about the Not-Invented-Here Syndrome

.NET Development Optimizely (Episerver)CMS Website Improvements Tips and Tricks Tech Talk

December 21 2023

Christmas Countdown: #4 Editors? It's just John and Jane, they know all the quirks - why does edit-mode matter?

An audience that is often neglected are the editors / content creators. That is a shame because happy editors => efficient editors => good content => great online experience.

CMS Optimizely (Episerver)Website Improvements Tips and Tricks Tech Talk

December 20 2023

Christmas Countdown: #5 Sure, our servers are locked up tight in the basement!

Securing your website is as important a topic as it is large and complex. In this post I will not go into too many details, but highlight a few problems I often see in Optimizely/EPiServer CMS implementations.

.NET Development CMS Optimizely (Episerver)

December 19 2023

Christmas Countdown: #6 "We LOVE content models - We have _all_ of them!"

The above statement is almost as scary as this: "Content Modelling - is that really needed? We just have one!"

CMS Optimizely (Episerver)Website Improvements Tips and Tricks Tech Talk

December 18 2023

Christmas Countdown: #7 DDoS? What's that? What do you mean 'prepared'?

Is your website ready to handle intense usage scenarios like DDoS attacks or black friday? Many people think that testing performance is the same as testing for load - but it's not and sometimes it might even work against each other.