Code you and us
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.
A client of ours asked us a while back to implement Azure B2C authentication for their Episerver implementation. The client is running 15+ websites, each on their own TLD for global presence. They are running their website all over the world, from The Netherlands, Germany, Brazil to China. Note, the websites are not running on a separate subdomain, which is implemented out-of-the-box (and allowed) using Azure B2C. In this blog I will describe the hurdles we had to take to get Azure B2C working on multiple TLD websites.
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.
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!”
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.
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, whow that’s a mouth full. But ohw yeah, it is at least as cool as it sounds!
