Article | by Chris Yapp
EPiServer Ascend 2018: Product stories, headless CMS and more
Armed with a handful of developers, marketers and digital execs, we attended Episerver's 2018 event in London. Here's what we learnt.
Article | by Chris Yapp
So as I was saying back in May, me and few of the other developers from Freestyle descended on Episerver Ascend (I know, it comes naturally, in case you were wondering), the highlight of the day for me (apart from the free bar – cheers Episerver) was the introduction to Episerver’s Content Delivery API, or more commonly referred to as a Headless CMS….
Now if you’re not a developer or in the space of CMS Development you might not understand why it’s a big deal or what in actual fact a headless CMS is, so I’m going to try and explain the difference between a normal CMS and Headless CMS, and what I see the benefits of adopting a “Headless” approach when developing CMS’s are.
CMS frameworks such as Episerver are traditionally known as monolithic applications – what’s a monolith? – in its basic form, a monolith is data storage, back-end code tied in with a front-end views/templates, which then typically gives you a single application – a monolith. These applications, or CMS’s in our case, are often web-first applications, meaning we create them so that all the content will be delivered via HTTP and served up in the form of HTML.
A few years ago it was safe to assume this was fine and all that would ever be required, and it still is in a lot of cases. However, if we want to deliver content through something other than a web app or website, say a smartphone/watch app or even a virtual assistant such as Alexa, then a monolith application/CMS would be incapable (without extensive modification and a world of pain from a developers point of view) to deliver its content through these channels. This is because web-first applications are tightly coupled, meaning that the content or data is very tightly knitted together with the front end presentation, all bundled up together to deliver one application.
So in its simplest form, a standard CMS application gives us 3 things:
Enter Headless…. A headless CMS is back-end only, with content being delivered through an API rather than baked into the front end presentation layer. The term “headless” comes from the concept of chopping the “head” off the “body”, the “head” meaning the presentation or display and the “body” being the content/data and back end code.
So if we compare this to a regular CMS, a headless CMS gives us:
So there you have it, an overview of what headless CMS is and how it works. Ultimately it's a more flexible and modern approach to developing a CMS, and allows for content to be delivered across multiple platforms and channels, resulting in your content having a wider reach.