Episerver's new Headless API offers a hybrid architecture for coupled, decoupled, and headless scenarios beyond your website. A competent REST API and extensive integration points surround the Episerver CMS to project your content into any number of applications. 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.
A traditional CMS includes a content repository and the means to transform raw content into a visual representation directly rendered in one channel – your browser. A Headless CMS decouples the content repository from the presentation layer, enabling you to publish your content in any application via API data services. Episerver believes that a hybrid approach gives our customers and developers the best of both worlds. Episerver CMS is not a true Headless CMS and there aren’t currently plans to make it one, but we do think there are situations where supplementing your traditional Episerver CMS with a headless tool could be beneficial.
The new Headless API from Episerver enables you to pull content directly from the CMS, bybassing the presentation stack when necessary.
Deane Barker, Chief Strategy Offier at Blend Interactive defines decoupled and headless CMS and explains some of the technical details and scenarios of how Episerver can work seamlessly as a headless CMS