Over the past years working with Episerver, a common conversation I've found myself in is where someone is having trouble reliably deploying their application. It can be represented in a number of ways, but it usually comes down to:
1. Long Deployment Routines
2. Unexpected Behavior
3. Slow Deployment Cycles
4. Interruption in Availbility to end-user
At Nansen, creating editor documentation is part of our development process. I wanted to share how we implement our editor guides, and hoping to hear from others how they implement theirs.
Episerver provides an amazing framework for transactional e-commerce websites, but that's not the only way you can use it. We created a mobile application for our client which allowed them to make in-person sales. Here is a bit about what we did and why.
In this post, I will be describing how to add custom templates to your Episerver TinyMCE. Using templates can improve the content entry experience for your editors by minimizing the amount of editing that needs to be done.
In this post, I will be describing how to add a custom editor view in Episerver that will be used to render documentation. Our example will be pulling the documentation from Github but I will discuss how the implementation can be extended to pull documentation from other sources.
