Headless CMS. The New Way to Deal with Content.
 

There was a thread recently by someone wanting a CMS solution for their adult website.

I suggested to the poster that a Headless CMS was the way to go, however there seems to be some confusion about what a Headless CMS is.

Unlike Wordpress, ElevatedX, Drupal, etc a Headless CMS has no front end. It's a place where any content can be managed and stored in any way you want with any structures you want and then allow a front end to query that data via an API.

The benefits of a Headless CMS is that you can have all your text, images, videos and other data in one system yet deploy that content to mobile apps, websites, television apps, game console apps or to any app or device you can think of.

Here's a video explaining some of the basics of Headless CMS systems and an introduction to each of them.

I hope that some of you find this useful.



If you have any questions about how you can use a Headless CMS in the real world, ask me below and I will help as much as I can.

Am I understanding correctly that it is basically a database designer?

It depends on the Headless CMS, however in most of them yes it allows you to design a custom data structure for your content. Headless CMS platforms are much more than that though, they also present all your data, or allow the updating of data via an API or SDK.

The true benefits come when deploying content across several platforms. For example a network of paysites could use the same Headless CMS and use the API to pull content relevant to that site. Or sites could be presented in different formats using the same data.

Decoupling also adds better security, meaning that your users will never be accessing a site which is used for content and data storage, they will engage with a light weight front end that accesses the back end separately through secure methods.

nope, cyberseo works only on wordpress

He could make his script run on anything; he does Wordpress because that's what people want.

He could make that shit run 10 times faster without Wordpress if he wanted to.

:2 cents:

Thanks asshole - Now I have a whole new thing to look at...

You're welcome :)

i guess, thats how cj sites are working, set up one centralized server with data.,

and create cj tubes farm and use API to query data.,

new tamplets, new keywords for each site.
but results will be same.

What I can't understand is how's possible to handle content.

Lets say that I want to upload a video as admin. No encoding, no runtime checks, nothing.

With a custom php script you write some code where, after hitting the submit buttons and checking that all things entered in the form are correct, the "temp" file is moved into a given directory with a given name etc etc.

How's possible to achieve the same result with an headless cms? I started studying Directus.

Easy, you build a handler. In different Headless CMS this is done in different ways.

In Directus you simply extend the multimedia component to automatically fire a background task to run ffmpeg on the video, create thumbnails and extract meta data which will then automatically populate within Directus.

I've built this exact thing with Directus, it was quite easy for me but I am a coder. Directus is open source so anyone can add stuff like this with ease if they have a little coding experience.

To give you an idea of the benefit of using Directus over custom code to do this, it cut the development time to about two hours compared to a couple of days.

Remember that with all headless CMS you still need to build your own frontends or apps to deliver the content stored in the CMS.

I understand that you are just finishing writing your own plugin on non-wordpress cms?

:1orglaugh:1orglaugh:1orglaugh:1orglaugh

I don't think this approach will ever come close to replacing wordpress. The only benefit I can see is it being decoupled and lighter in general. You can already pull data from the wp database through the WP API and I am doing just that with a new app I'm developing.

The wordpress ecosytem - with all those themes and plugins is just too strong, plugins allow you to plug and play alot of complex functionality that you would have to develop for yourself if you were using a headless cms.

I can see the benefit to some use cases (eg. when you want to structure your data the way you like etc.) but for the average person, wordpress is still the way to go.

Do you know any video or tutorial about doing something like that (maybe not exactly what the example I showed)? Just to have a grip to start from.

One of the big advantages of decoupling is the ability to run a distributed system. If you're deploying a mobile app that has any kind of user load then Wordpress won't cut it. With systems like Cockpit or Directus you can run a distributed load balanced system which will handle loads of thousands or tens of thousands or hundreds of thousands of users.

Even relatively modestly successful mobile apps have a huge demand on resources, Wordpress would just collapse under the load.

It's all here https://docs.directus.io/extensions/...re-explanation

Without trying to sound condescending if you can' work out how to implement what you need from the documentation then hire a coder.