Christmas Countdown: #11 Dependency Injection is not as easy as it seems
Dependency Injection is an extremely useful pattern. It has been used with EPiServer CMS for years - and with .NET Core it has truly become the go-to method of coupling your business logic together. However, once you start having services depend on other services their lifetimes can give some unexpected difficulties.
Christmas Countdown: common Optimizely CMS Pitfalls - #12 Picking the right add-ons
12 days to Christmas and here is my countdown list of the top 12 common pitfalls I see in Optimizely CMS implementations - along with some tips on how to avoid them. Today we'll take a look at #12 on the list: Picking the right add-ons
Live on Optimizely CMS 12 and .NET 8
"Better late than never" is a fitting saying here. We've finally gotten around to updating the CodeArt.dk website to Optimizely CMS 12 and .NET 8!
Optimizely Search & Navigation - Get autocomplete suggestions in right language
When you are using Optimizely Search & Navigation (Find) to help you generate autocomplete suggestions server side in a multi-language scenario it can be tricky (and poorly documented) to figure out how to get the suggestions in the correct language.
Easy property inheritance in Optimizely CMS
Ever needed a way to inherit property values down through the page hierarchy in Optimizely CMS 12? Now there is an easy way to enable that.
Make some asset types download automatically in Optimizely CMS 12 using the Digizuite integration
Here is just a quick tip for how you can do custom blob http handling when using the Digizuite integration to Optimizely (Episerver) CMS 12.
When best practice isn't the best - Dependency Injection and Optimizely CMS
Some people live and breath 'best practice' development. I am not one of them. Risk is, in-experienced developers (or sometimes experienced) might use them just cause they are 'best practice' and not think more about it. Even when it turns out they are not. Here is little example...
Automatically have Optimizely Content created in the correct place
A classic problem is that you want better structure and governance in for example your blocks. Maybe you have a policy to have all Banners or FAQ items in a specific folder so they can easily be found and re-used across the site, but way too often editors take the 'easy' approach and use the "Create a New Block" option in a content area - which by default places the block in the "For this page" folder, rendering re-use impossible. Here is a simple solution to that.
Running Optimizely CMS 12 (Episerver) on a Raspberry Pi
.NET Core is cross platform. But can you really run Optimizely CMS 12 and everything needed on a tiny ARM based Raspberry PI? Yes you can, and it's not that hard.
AI Assisted Content Creation - in Optimizely CMS & Commerce (AI Series - Part 2)
AI assisted content creation is an exciting new approach driven by algorithms and models like GPT-3, DALL-E, Stable Diffusion and more. At CodeArt we've been experimenting how to use these technologies to enhance the editorial process. In this second part of the blog series on the topic I'll share a video of a prototype integration to Optimizely (Episerver) CMS of content creation using AI for both images and text.