This is the 2nd article in a series of articles on creating an engaging customer experience utilizing Episerver blocks. To help set the scene for what we will be going through please read the introductory post.
My coworker and I ran a lab at this year's Episerver Ascend conference. In this lab, we went into detail about all the benefits of PWAs (Progressive Web Apps). We also walked through some tools and techniques for integrating them into your site. I wanted to share a bit about the lab, including some common questions we received.
It's no secret that security is vital for different areas of an Episerver website, especially the editing and admin interfaces. If you use Azure Active Directory to login to organization infrastructure already, why not use it to secure your website? Optionally, you can use Azure AD to shield non-production environments from public view entirely, allowing you to develop new features and content without the public's eye on them.
Since my last post about Episerver TinyMCE default templates, I have worked on several projects that could benefit from them. I decided to create a NuGet package of some generic templates that I think most projects could benefit from.