Recently I came across the term Headless CMS. what they are , why we use them and which one to choose as I am MERN stack developer with Next.js.
For further actions, you may consider blocking this person and/or reporting abuse
DEV Community
Timeless DEV post...
Git Concepts I Wish I Knew Years Ago
The most used technology by developers is not Javascript.
It's not Python or HTML.
It hardly even gets mentioned in interviews or listed as a pre-requisite for jobs.
I'm talking about Git and version control of course.
Read next
Cryptographically protecting your SPA
Matheus Adorni Dardenne -
Deploy React.js application on Render
Ahmed Saber -
Unexpected Moments of JavaScript That Will Challenge Your Understanding of the Language
Code of Relevancy -
STM32F4 Embedded Rust at the PAC: UART Communication
Omar.unwrap(); -
Top comments (2)
Headless CMS is just a CMS where you can plug a front-end to call APIs directly to display your content.
It is usually a separate component so it helps a lot in speed & performance. This makes it easier for different people like marketing to focus on using/editing the content in the CMS or you calling the API from your front-end without dealing with the backend. Since headless CMS offers great documentation in their API to make it easy to pull data from the CMS.
A headless CMS is a content management system that provides the Data over an API. The term “headless” comes from the concept of chopping the “head” (the front end, i.e. the website) off the “body” (the back end, i.e. the content repository). A headless CMS remains with an interface to add content and a RESTful API (JSON, XML) to deliver content wherever you need it.
The Headless CMS I love is Directus: directus.io/. Not sure you are experienced with Wordpress, but you can also use WP as a headless CMS with the API they provide: developer.wordpress.org/rest-api/