...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
The Image point editor for Episerver CMS can be used together with the Picture helper in ImageProcessor.Web.Episerver to control the cropping of images. If showing the same image in different height and width on your site, you might want to control how the image is cropped. Let's say you are showing super cool, wide image … Continue reading Control the cropping of your images with a focal point
Earlier this year i wrote about a solution for optimizing the images on your Episerver site. Since then, that solution has been included in the ImageProcessor.Web.Episerver nuget package. With the Picture html helper included in the nuget it's easy to optimize the images in size, quality, and file size. Images will be responsive, and can be … Continue reading A dead-easy way to optimize the images on your Episerver site.
Optimizing the file size for the images on a site can really improve page load time. This article shows how you can use ImageProcessor to minimize the size of your images. UPDATE: The Picture Html helper described below is now included in the ImageProcessor.Web.Episerver nuget. Read more here. I'm extending the solution for responsive images … Continue reading Optimize your images with ImageProcessor
By using the picture element together with ImageProcessor, you can create a robust solution for responsive images. With this solution you can very quickly make sure that you at least don't serve way too big images. Once that is done, you can add more image sizes and fine tune the media queries, to further optimize … Continue reading Picture element + ImageProcessor = responsive images made easy