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…

Finally it's time to release administrative user interface for complementing Asp.Net Core application localizing process. It's been a while since localization provider has been released for Asp.Net Core applications, but until now - actual translation of the resources was limited due to absence of the user interface through which editor can make adjustments to the translations. I'm happy to announce that AdminUI has been rewritten to utilize Vue.js framework and to grind some of the rough edges of the library. Installation The only thing you need to…

This post shows all the necessary changes I had to make to convert original pizza solution to use MediatR library (+ also converted to NetCoreApp 2.0).…

Localization provider is well and alive. Lately I've been heads down busy with porting some of the parts over to .Net Core targeting .Net Standard version 2.0. Anyway just wanted to let you know some of the smaller updates and fixes for the latest version of the provider packages. Multi-Target -> NetFx and Core Now there are specific multi targets for .Net Framework and .Net Core for and packages. This was required due to reported issues when package was used context together with WebApi (to be more specific…