Blogging about web, mobile, and whatever other tech stuff I come across. I work a lot with content management systems. I am an Episerver MVP, and a Contentful certified developer.
_ _ ___ __
| | | | / _ \ / /
__| | ___| |__ _ __ _ _| | | |/ /_
/ _` |/ _ \ '_ \| '_ \| | | | | | | '_ \
| (_| | __/ |_) | |_) | |_| | |_| | (_) |
\__,_|\___|_.__/| .__/ \__,_|\___/ \___/
A client came to us needing a recommendation for a headless CMS to run multiple portal applications. With the requirement that we provide a headless option, and the knowledge that the editors love Episerver's features, it took us all of two seconds to come up with Episerver's Content Delivery API as a solution.
Content modeling can be a tricky thing. If done incorrectly, it can cause all kinds of headaches for editors. And trust me when I say going back to update the structure of your content after your project is live is worse. It's something you want to get right the first time.
The concept of signing applies to more than messaging and encryption. I wanted to give some examples of how you could start signing your work as a developer. I will be walking through how you can sign your git commits. As well as any files/packages you build.
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.
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.
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 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.