Originally Posted by AdultKing

If you're deploying a number of sites a headless CMS is the way to go these days.

Not everything is presented on the web anymore and websites aren't necessarily the only thing you need to get your content to.

A Headless CMS is a CMS like Wordpress but without a front end. All the pictures, images and text and any other content are retrieved via an API.

That means you can deploy lightweight Web based front ends, Apps, IoT projects, access your data on Watches, Phones, TVs and any other device you can think of.

It also means, for a webmaster, that you can run a lightweight code only site on the front end, using any templates or web technology you like without worrying about the content, because the content is managed from a single instance of whatever Headless CMS you deploy.

From the content side, it means you don't have to worry about how to display large amounts of content, because you have the freedom to deploy these lightweight sites to suit the content you have. In one place you have have a massive amount of content with better tools to manage it, search it, scale it, edit it and multiple data types of content not just pictures, video or images but full collections, for example you can have multiple galleries of images and retrieve a whole gallery as a single collection, or.a category of galleries as a single collection.

For some people it's overkill but for many people it completely changes the way things are done for the better.

Wordpress has an API but it's not the best, in fact it's one of the worst CMS to use as a Headless CMS. There are several better solutions.

If anyone is interested in the subject I'll start a thread on it.