Enonic is headlessMorten Eriksen on
See what headless capabilities Enonic offers, and how we can help your organisation.
Enonic can provide your organisation with a powerful headless CMS—complete with a robust GraphQL API to distribute content to any channel. But we are not a pure headless vendor, as we give our customers the choice to use headless and traditional CMS capabilities together in what we call a hybrid CMS.
However, you can use Enonic only for headless delivery if you wish, in a manner that is just as flexible and lightweight as the pure headless platforms on the market. Enonic’s headless solution is fairly new, but current exciting use cases include Norsk Tipping, the Norwegian Directorate of Health (Helsedirektoratet), and Schibsted.
So, what exactly can you expect of our headless solution?
See how Enonic fits your current architecture and skill set:
More than a CMS
Our headless CMS is part of a larger platform called Enonic XP. In this open-source web application platform, developers get access to the essential services required to build custom applications in a single dependency.
See also: 5 reasons to go headless with Enonic »
Headless out of the box
The content model of Enonic XP requires that every content item must be of a specific content type. This ensures structured data, allowing every item to be treated the same way—whether it is pages, author profiles, case studies, images, PDFs, sites, folders, or other custom content types.
Enonic is thus a content-oriented CMS, as opposed to a page-oriented one. This is of tremendous importance if you are interested in headless—as structured content makes Enonic XP ideal for delivering content to any channel via an API.
Out of the box, Enonic offers headless capabilities through GraphQL, which can be accessed through our headless CMS starter kit—based on the Guillotine project. This open-source library can be customised, but you can also build your own custom APIs to deliver content as you deem fit.
Optionally, content items can be set up with pages in Enonic XP. The platform supports page templates, page components, and reusable fragments—making it ideal to build landing pages in conjunction with headless distribution, or just to allow for previews.
Applications can thus be built to deliver renditions of content, preview, APIs, or to further extend the functionality of the content management system. In Enonic XP, it is possible to build and deploy multiple separate applications to offer complex functionality, all while developing, deploying, and maintaining them individually.
Learn more: 6 reasons to choose Enonic as your hybrid CMS »
A central part of any headless CMS is form-based data, and Enonic XP includes a schema system for building forms. The system is built on top of the low-level NoSQL storage and can read, validate, and store data as properties of specific value types.
Input types are the basic building blocks enabling editors to create content. In Enonic, input types include TextLine, ContentSelector, MediaSelector, date, HtmlArea, and checkbox. Input types can be directly used to build a form, but they can also be combined to nested structures within a form. ItemSets and OptionSets can be used for the purpose of further grouping nesting input types.
Enonic’s schema system is loosely coupled, as the data is stored in the repository while the schema is placed in code. The schema is only applied during saving for validation, and the data can exist without the schema. Schemas can thus be updated without having to upgrade the data, and the data can be migrated when needed.
Also, all stored data can be accessed through APIs or through import/export functionality.