There are sometimes moments when you just need to take deep inhale and add backward support for apps that most probably you will hardly see selected in "File > New Project". We do have some projects still based on "pure" Asp.Net Mvc that need client-side localization. Therefore adding support for this type of apps sounds like feature with "must have" label. At least for now. This applies to v5.5.1 and forward. However, if you are targeting .NET Core - support is…

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…

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…

Apply DisplayOption for EPiServer.Forms Elements Would you like to use this feature also for EPiServer.Forms? In this blog post I'm gonna show you how to do that. Background It's really great to see platform evolving and adding new features. But unfortunately - I must say that EPiServer.Forms are pretty close for modification (which is good) but at the same time - not so open for extensions, that's why we will need to modify some of the built-in templates to get this done. Getting Started First of all,…

Here comes small updates for the Content Area renderer in the latest version: Now EPiServer.Forms are supported Possibility to have your own Css classes DisplayOption is now available in block template as well (if needed) Some smaller bug fixes Naming Challenges As you might know - I'm still struggling with naming of this package. Originally it was planned to be as Twitter Bootstrap Content Area Renderer, but apparently over time package feature set deviated from original idea as now package gives so much more than just adding necessary Css…