The headless architecture is the core feature of the technology and is what differentiates it from a regular content management system. As the regular CMS takes care of both the content management and the content presentation, the architecture can be said to be coupled. Managing content is tightly connected with presenting it and both parts are controlled from the same backend with dependencies between the two. The headless architecture splits these two and a headless CMS only takes care of the content management - creating, reading, updating and deleting (CRUD). Once your content is created it's not automatically presented, but instead made available through RESTful APIs. Here your content will be waiting idly for a frontend platform or framework to pick it up and present it in the way it wants to present it. This effectively means that you decouple content management from content presentation and break up any dependencies between the two. So if your back-end developers and content editors prefer working in one system, while your front-end developers prefer a different one, it is possible with a headless CMS. All the front-end developers need is for the content to be available through APIs, then they can connect it to the front-end and display it in any way they want - on any device or platform. So if you go with a Headless CMS, the headless architecture demands that you use (at least) two different platforms: The headless CMS for handling all of the content and a frontend platform to present the content.