Everyone's going headless these days, and it's hard to blame them: this is arguably the hottest trend in web development right now, opening up dozens of powerful new options for organising the front end delivery of web content. So what does it mean?
A 'headless' or 'decoupled' CMS is simply one that has detached itself from delivering themed content and offloaded this responsibility exclusively to the front end.
It's easy to appreciate the benefits of this headless approach, with the obviously superior organisation it brings to a project, and also the flexibility it affords front end developers in realising a design. The power to render content is now entirely in the hands of the front end developer. Common complaints from the past quickly evaporate: 'this is how the CMS does forms', 'this is how the CMS does tables', 'this is what's possible here, this what's not possible there' - the rendering restrictions of the CMS are no longer a barrier to delivering the promised design, because rendering isn't the task of the CMS anymore. It's the task of the front end application that's feeding from the CMS via an API.
The headless CMS is made a reality thanks to technologies such as Angular2, which is invaluable in smoothing the transition from the tangled development CMS processes of old to the fitter, faster headless CMS of today. With the numerous benefits of headless development, there's virtually no convincing argument for returning to the old process of CMS construction, but there's every reason to make your next CMS a headless CMS.
To discuss this topic more with us please get in touch.