Hybrid headless architecture gives you the best of headless CMS and traditional CMS
Episerver can serve as the central content hub for your organization, providing a single-source for content across the entire array of your digital properties.
How headless CMS works
With a traditional CMS, the CMS controls how the content is presented. The "head" is responsible for generating the HTML that is parsed and rendered by the browser. A headless CMS, on the other hand, is back-end only. It acts as a content repository that makes content accessible through REST APIs for display on multiple devices.
The headless CMS does not know how content is presented. It is a specialized database, serving content that is transformed into HTML by other systems.
Examples of when a headless approach is useful:
- To provide content for native applications that are not HTML-based.
- To integrate with a Point of Sales (POS) network, linking different output systems.
- To manage content for legacy platforms inside Episerver.
How Episerver's headless CMS works
Episerver's headless API lets you pull content directly from the CMS, bypassing the presentation stack when necessary. Our REST API uses our enterprise search solution, Search & Navigation, to provide an easy way for developers to use the content and not just get items by ID.
With the user interface separated from the application logic, you're free to choose the tools, frameworks and technologies necessary to provide the best possible customer experience in every channel.
The Essential Guide to Decoupled and Headless CMS
Deane Barker, Senior Product Strategy Director at Episerver, defines decoupled and headless CMS and explains some of the technical details and scenarios of how Episerver can work seamlessly as a headless CMS.Download report