Tag dit Episerver website videre til næste niveau sammen med CodeArts Episerver ekspert og online hold.
Hvad enten I skal starte på et nyt web projekt, eller har behov for at identificere og implementere forbedringer på jeres nuværende så står CodeArt klar til at hjælpe.
Vi får et kick ud af at hjælpe vores kunder med at levere en online oplevelse ud over det sædvanlige og ser muligheder hvor andre ser problemer. En god løsning for mange er et fast abbonnement på X antal timer hver måned hvor vi både hjælper med at løse de mest hastende problemer - men også rådgiver, planlægger og tager jer videre på jeres online rejse. Subscribe to success
Vi har også god erfaring med at holde workshops hvor vi gennemgår jeres nuværende løsning og på baggrund af den foreslår optimeringer og forbedringer som nemt, hurtigt og billigt kan forbedre hvad I har.
Læs mere her:Website Service Check
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.
New Project: Optimizely (Episerver) Health Checker
Wouldn't it be nice if there was just one place you could go and get an instant overview of the health of your Optimizely (Episerver) installation? With checks that are both technical, functional, business and covers product, addons and implementation? Here it is. Or at least the start of something that could be very useful.