Provide Optimizely (Episerver) Expertise
Evolve your website with a team of dedicated Optimizely (Episerver) and online experts.
Whether you are looking to build a brand new omni-channel online presence on Optimizely (Episerver) technology, evolve your current platform step-by-step or have workshops to inspire you as to which steps you should take to make the most of what you currently have, it all becomes a lot easier when you have a the right people on your side.
At CodeArt we love helping our companies evolve their online presence by providing some of the best expertise on the market.
You can for example in-source a permanent expert X number of days a month:
Or start up with a 2 day workshop where we evaluate your current online presence and inspire you to easy improvements:
Content Report Generator v.2.
When you are about to migrate a site from CMS 11 to CMS 12, it's not unusual to want to do some rewriting and re-implementation to clean up the architecture as part of the project. When you do that (and in many other cases) it can be incredibly helpful to have a handy overview of your content, it's usage and your visitor groups and their usage. Here is an easy way to get that.
Optimizely CMS: List content recursively on a page - and list the visitor groups used
Quite often a lot of the content on pages in Optimizely Content cloud (aka Episerver CMS) is structured in blocks placed in content areas. And often even blocks in blocks. Sometimes it's needed to quickly get a list of all the content items on a page - and sometimes you might also be interested in which visitor groups are used. Here is a couple of extension methods to help you with that.
Self service with Fluid Templating for editors in Optimizely CMS
A classic need in many websites - especially self-service sites - is a placeholder mechanism, so editors can use placeholders in their text to be replaced with user specific data. Recently, working with a client, we ran into this problem and tried out a new approach to empower the content creators to solve this themselves.
Secret debug tools in Optimizely CMS 12
Secret treasures are always fun. And when I was examining the endpoint list from my previous post, I noticed a few hints that I couldn't leave unexplored. It turns out that just as the previous versions, Optimizely CMS 12 comes with a couple of hidden debug gems.
Listing all endpoints in Optimizely CMS 12 / .NET 5
Routing has significantly changed in .NET 5 - and that affects many parts of Optimizely (Episerver) CMS 12. For example we have to get used to endpoints a middleware. As I am working on upgrading a few different add-ons I found it could be useful to see which routes are registered out of the box.
Anti-Pattern: Don't modify Optimizely CMS (Episerver) content objects in the Controller
Using your content object (CurrentPage / CurrentBlock) as a makeshift viewmodel where you change settings or extend it with user data in the controller before passing it to the view, is unfortunately (and to my surprise) a pretty wide-spread practice among developers implementing Optimizely (Episerver) web sites. But it really needs to stop.
Optimizely (Episerver): Split folder structure for blocks and media
Since version 7 or 8 of Episerver (now Optimizely CMS), the shared Blocks and Media have been sharing the same folder structure. Some people see a benefit with the shared structure, and some absolutely hate it. Personally, I have gotten used to it - but I was recently asked if it's possible to split it up. Here's the hack I came up with.