Having couple of initializable modules Episerver solution - and everything works as expected. But what really happens under the hood and how Episerver initialization system really works?…

There been couple of times when we have presented Episerver and Azure Functions (aka "episerverless") and how they play well together. However, looking at overall our sample application architecture - it still seems to be a bit brittle and composed together out of some small moving parts.…

Freshly baked v5.0 is out now. Changes in this version (some of them are breaking ones). Mostly release was focused on .Net Core AdminUI improvements and new features.…

And here we are again to talk a little bit about localization stuff. Most probably you know already there are pretty neat settings when it comes to localization of the Episerver and how one should behave when resource translation is missing for requested language (or culture to be precise). You can define fallback behavior, fallback culture and maybe in the future even something else. ... <localization fallbackBehavior="FallbackCulture"> <providers> <add name="db" type="DbLocalizationProvider.EPiServer.DatabaseLocaliza <add name="languageFiles&…

Background With latest hype around Episerver with no head (aka headless) - it's becoming more interesting to escape casual back-end stack and see what's happening in other fronts. And it's not surprise that Episerver content could be consumed in other client-side platforms. So this time decided to explore a bit more my colleagues work and look how React is doing nowadays. Anyway at some point React component will come to conclusion that there is a need for getting some translations from the server to render localized components. And this just…