One session I presented at Episerver Ascend London, Stockholm and Benelux 2018 was on Episerver as headless. This specifically talked about Episerver's approach to headless, including advantages and disadvantages of the approach. I also showed some examples of how the Content Delivery API (the Episerver headless API) could be used.
This post shares the code and presentation ran in this session.
Exploring the API
This section showed what could be done with the Content Delivery API. It simply installed the Content Delivery API onto an Alloy site and used Postman to explore some of the capabilities such as loading a page, querying for content and expanding content areas to retrieve multiple pages/blocks in a single request. An example can be seen in Postman below:
One of the sessions presented at Episerver Ascend London and Stockholm this year was called connecting Episerver Insight and Campaign. This presentation discussed how Episerver Insight and Campaign could be used together to create some user experiences that understood a customer's on-site and off-site interactions. Specifically it showed how Episerver Insight and Episerver Campaign could be used to create an on-site experience that was affected by off-site behaviours measured by Episerver Campaign (in this case interaction with email but could also be push notification or SMS).
The demo scenario is as follows: