The strength of a traditional CMS like Plate is that you manage and organise the content and the front-end, i.e. how the website looks, from one environment. The content is always connected to the form that you give it. For example, you define the design of a product page in the CMS and at the same time you determine how the content should behave and make it possible to add content for that product page.
Whereas with a traditional CMS, content (back-end) and front-end are intertwined, a headless CMS separates the two parts. In the back-end, you organise the information in models and with the help of APIs, you can send the information to the right channels (website, apps, etc.). This way, one product in your headless CMS can be shown in multiple places in different guises, which is of course super efficient, because the same content no longer needs to be added separately in different places.
With a headless CMS, you have complete freedom to design your channels on the front-end. You are not dependent on the CMS you use, but can, for example, use modern front-end frameworks such as Vue.js, Angular or React to set up the ideal front-end solution for your customer.
A CMS variant commonly used is a decoupled CMS. A decoupled CMS is in between a headless CMS and a traditional CMS. A decoupled CMS has a back-end and a front-end that are disconnected by an API. So you have the possibility to develop a specific experience for an app or another channel. Most traditional CMSs today already work as a decoupled CMS. The Plate CMS also already works decoupled, where you can use our API to retrieve content to other devices.
At Plate, we are well on the way to making our platform headless. At this moment you can already use Plate decoupled. For Sogeti (part of Capgemini) we developed an e-learning platform in Vue.js and use Plate decoupled.