Unmapped? ContentProviders

The CMS is not the only place where content is served from. A modern website does present content from different sources like; Video platforms, DAM systems, PIM systems or even other “content networks”. We do consult on a couple of integrations where we have the need to deliver from these kind of sources. Content Providers to the rescue. In this post I am going to share some challenges we have experienced down the road, especially in relation on the IdentityMappingService.

Serving the context

The beauty of a system like Episerver is that you can rely on default patterns and practices. In this post I like to show you how you can deal with context related stuff by using a pattern we use in every other application architecture as well.

Sneak peek; What bigdata can do for your CMS

The combination of big data / analytics and all the nice things that we can do with it in our CMS systems has keeping me busy the last 2 years. The result is our own CMS independend bigdata platform where we can combine analytics, personalisation, testing and connecting other datasources like (CRM, ERP etc.) In this blog post I want you to give a little sneak peek of what we did.

Cross session personalisation with Episerver

With the standard visitor group criteria cross session personalisation is not standard.
However when a user already has visited your website you know him or her from a previous visit and don’t want to discover who he or she
is the second time, you only like to know him better. In the real world the customer don’t need to introduce him self the second time.
We like to reach the same goal with the visitors on our website.