In On-Page Editing mode, Episerver will create a blue border around all editable properties. This feature is very useful. However, if you have a lot of properties on the page, it may be challenging to locate the correct property, and editors may be using All Properties mode more often than On-Page Editing.
When some files are missing in a git repository, or they don't have the correct Build Action in the project, a build server may deploy a bad artifact to the production environment. One way to detect this and stop bad deploys is to set up unit tests.
Building a multi-language website is always challenging. Among other things, we need to think about date formats, language analyzers, and full-text search. However, we must also not forget the site editors and provide them the best possible editing experience.
When creating new page types, developers mostly use the EPiServer CMS Visual Studio Extension or copy and paste the code from existing files. In this blog post, I’ll show you how to create EPiServer page types using ReSharper file templates. Once you learn all the shortcuts, it becomes much faster to generate code using ReSharper, rather than copy and pasting.
After a few development iterations it can be difficult to keep an overview of all content types and their properties. We can always look in Visual Studio or click through different menus in edit and admin mode, but that’s just too time-consuming. It would be nice to have all that information in one place, in a user-friendly format, and be able to filter and export the data to a PDF file.