The term Headless was coined a italy girl whatsapp number while back, when pioneering content management systems like Ibexa (then eZ Systems) or startups (at the time) like Contentful started decoupling the “head” (aka the website) from the body (aka the content and services pulled from the website) by focusing on simply delivering content to other applications via their APIs (in Ibexa’s case, via GraphQL and REST APIs). Ultimately, the goal of decoupling was indeed coupleability and agility – two key components of digital innovations; and it proved to deliver on that promise.
Perhaps the term Headless is not that meaningful and I think we could replace it with the term Dockerable. No matter the term, the winning concept is to think of the functional and business components of a digital application as services, all interacting through APIs and tied together in different user interfaces, including websites – the head.
You might think that using terms like “head” and “body” implies a single website “the head.” That’s somewhat confusing – the goal is to have multiple heads as well. That’s where Ibexa’s multisite capabilities and front-end management tools come into play.
Specifically, how does a headless content engine benefit your business in terms of agility and efficiency?
Shape your content without restrictions and with complete freedom
With a content engine that is independent of the delivery channel, the headless CMS allows your organization to create a content model that is perfectly suited to your business domain and can evolve without heavy impact and ties to an existing framework or larger application. This means that modeling your business content is much faster and easier.
