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&…

This blog post is about how to fix Asp.Net Core Mvc built-in client model localization provider and use DbLocalizationProvider on client side as well.…

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…

After gratefully accepted invitation to contribute to the Episerver Developer Tools package, I can safely do this: All credits to the amazing Episerver team, I'm just contributing here :) So that's why happy to share some of the updates in latest version. While reviewing performance for startup modules (either configurable or initializable ones) to find out some bottlenecks on the site.. I had hard time to find the answer on question - what is the order/dependencies of modules in this list and how they are interconnected? As I do like…