The Picture helper for Optimizely CMS 11 now supports creating webp versions for "all" image formats. Up until now webp versions was only created for jpg images. The reason was that the webp versions where lossy. The webp versions of a png image would get grainy/blurry parts, instead of the solid colors in the original … Continue reading Updates for Optimizely CMS 11 Picture helper
Say hello to PictureRenderer.Optimizely! The html helper that makes it super simple to render HTML Picture elements in your Optimizely CMS 12 solution. Images are automatically cropped and resized, and the browser will always select the most optimal image to use.The result is optimized (width, format, and quality), lazy loaded, and responsive images. If you … Continue reading PictureRenderer for Optimizely CMS 12
This blog post is about speeding up your site by caching your Episerver Optimizely CMS pages in a CDN. This solution gives you granular control on how long a specific page should be cached. It works for any CDN, but here I'm focusing on getting it to work with the Cloudflare CDN that is included … Continue reading Serve Optimizely CMS pages directly from a CDN.
This is my experience on how to get started with the preview version of Optimizely CMS. Expect this blog post to be outdated fairly soon... Finally I took the time to take a look at the brand new Optimizely CMS, the .Net 5 version of former Episerver CMS. It seems to be pretty easy to … Continue reading Getting started with Optimizely CMS preview
...and just call it a CMS? Sorry for this grumpy-old-man-rant, but isn’t it time to retire the term “headless” when we are talking about CMSs? It’s not needed, and it doesn’t really mean anything. If you search for a definition of the term “headless CMS” you might find something like: a CMS where the content … Continue reading When do we stop using the term “headless” for a CMS?
It doesn't really matter if you use Powershell or Azure CLI to setup your Azure resources. It's more a matter of taste. Here is a quick comparision anyway 🙂
The Picture helper in ImageProcessor.Web.Episerver now have an option to render the loading attribute that enables browser-native lazy loading. This makes it even simpler to optimize the loading of images. If you are familiar with the Picture helper you might already know that there are options for rendering the picture element that supports lazy loading. … Continue reading Episerver Picture helper now have option for native lazy loading.
I have spent way to much time trying to set up code package deployment when using TeamCity together with Octopus deploy. Read this to avoid following my path to failure :-). Well, not complete failure, I did learn some new things about both PowerShell and Octopus... Update: "DXC-S" is now known as " Episerver DXP" … Continue reading (Trying to do) Code package deployment to Episerver DXC-S
Episerver recently released an API that allows partners and customers to automate deployment to DXC-S environments. If using this API you no longer need the manual process of logging in to the DXC-S portal and starting a deploy. The API also makes it possible to deploy directly to Pre-production or Production environments. Update: "DXC-S" is now … Continue reading Deployments to DXC-S using API with Octopus Deploy
The "Content output cache" is strangely enough a basically undocumented feature of Episerver CMS. It's strange, because the content output cache can be a simple way to really speed up your site. I will not go into details about how to set up Content output cache in this article. Instead I'll show a way to let … Continue reading Let Episerver editors control the output cache