Writers, editors, and publishers spend years becoming familiar with content management systems. They are expert CMS users, but they often have no desire or incentive to learn the underlying systems and code. They understandably want to focus on creating and publishing content — the CMS is just a tool. A headless CMS allows creatives to use the interface they are familiar with without imposing the constraints of an inflexible content management system framework on front-end developers and designers.
That’s important because with the freedom provided by a headless content management system, developers can iterate more quickly on the front-end experience, build different front-ends that take advantage of the same content, and access the most up-to-date web technology.
Historically, a headless CMS was complex to build and manage, but with the advent of the WordPress API, it’s a lot simpler. Sites like the New York Times and Quartz used WordPress as a headless content management system before the introduction of the WordPress API, but it was an expensive and time-consuming process, putting headless content management systems out of the reach of the average business. But today’s WordPress provides everything a developer needs to build a fully functional decoupled front-end.
A headless CMS offers the best of both worlds and that’s why they are becoming a favored option for ambitious front-end developers.