The web is constantly evolving and we constantly find new and different and sometimes, better ways of solving old problems.
One such evolution is the emergence of so called headless applications.
Headless applications use content management systems like WordPress as data resources and present the data independently.
Standalone applications that receive and send data from CMS’s such as WordPress and other data providers without actually being connected to them.
This allows designers and developers to break the confines of whatever CMS is used and instead work with pure data they can use and percent in any way they choose.
Pretty much the fulfillment of the age-old promise of total separation of content from its presentation.
A standalone headless application can be built using WordPress as a data provider with all communication happening through the WordPress REST API.
Headless apps are very much both the present and the future of the web.
A headless CMS is a content management system where the content repository “body” is separated from the presentation layer head. Some traditional CMS platforms offer an API that allows you to send content to a separate presentation layer. They call this “headless” because the presentation layer is separated from the body.
One way to solve the limitations of a traditional CMS is by implementing a “headless” CMS — if the presentation layer of a website is the “head” of a CMS, then cutting off that presentation layer creates a headless CMS. While this type of headless CMS enables you to choose an appropriate presentation layer for a digital platform, it doesn’t solve an underlying problem: structuring content so that it can be reused across different platforms and channels.