Decoupled and Headless CMS with Episerver

Decoupled and Headless CMS, with its single point of storage, promises to address the need for omni-channel content delivery and challenges the standard monolithic, multi-purpose CMS.

Deane Barker, Chief Strategy Officer, Blend Interactive
Deane Barker defines decoupled and headless CMS and explains some of the technical details and scenarios of how Episerver can function as a headless CMS.

The “head” in “headless” refers to the delivery tier of the entire solution. A headless CMS is one that delivers content via an API instead of concerning itself with templating and management of the delivery environment.

For marketers looking to focus their content delivery, this can be an asset. However, when you step back and consider the entire content management environment from end-to-end, this is a relatively small piece of the puzzle. 

"Episerver allows for both paradigms: traditional coupled website delivery, and headless/decoupled API delivery."

Headless content delivery doesn’t exist in a vacuum. Regardless of how it’s delivered, content still needs to be, well…managed. Editors need to be able to create, collaborate, and control their content. There are infrastructural issues to consider, such as user and group security management, content aggregation and architecture, reporting and versioning, etc. Download our whitepaper on Decoupled and Headless CMS and see whether headless is the way to go for your organization.

Complimentary download