Complex data using Episerver forms
About how to send context related data or other complex data to an external endpoint using Episerver Forms with valid JSON.
Author: Jeroen Wijdeven
The “container” practice
Containers seems to be a nice solutions, but it doesn’t always feel right to use this practice. I am going to share the considerations of using a container and share other features which maybe fits a “container use-case” better.
Cleanup blob storage
Sometimes I see blobstorages growing at customers side. It can be the result of a job, or because the storage is used by a couple of developers or because Develop and Test are using the same storage. For all these cases I have created this small script. Which does easily create a clean new container for you.
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 to the IdentityMappingService.
Language strategies
You will be surprised how many strategies are possible and what kind of decisions you can be made for handling languages. In this blog post I like to share some default strategies and thoughts about how to setup a multi-lingual / multi-country website.
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.
QA – Block rendering practices
A collegeau CMS developer asked me a maybe general but very important question the other day. Q; “When creating blocks, do you tend to put “structure” markup in block views?” A: “it depends!”
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.
Continuous Integration using Appveyor with the EPiServer Digital Experience Cloud
Continuous Integration using Appveyor with the EPiServer Digital Experience Cloud, whow that’s a mouth full. But ohw yeah, it is at least as cool as it sounds!
