Optimize images added in the rich text editor.

PictureRenderer for Optimizely CMS can be used to optimize images added in the rich text editor (TinyMce). In PictureRenderer.Optimizely v2.3 an XhtmlString extension is added that replaces img elements in the rich text content with a picture element. You enable this by creating a display template for XhtmlString properties. Create the file /Views/Shared/DisplayTemplates/XhtmlString.cshtml and add this: @using … Continue reading Optimize images added in the rich text editor.

PictureRenderer for Optimizely CMS 12

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

When do we stop using the term “headless” for a CMS?

...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?

Episerver Picture helper now have option for native lazy loading.

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.