Hi all! Welcome to my next blog. Today I am going to share about a tech meetup which was I attend recently. The meetup was organized by Code On JVM at Contentstack.
That was a great experience for me. The environment(Contentstack) was truly inspiring, such a great place to work and learn. We had three insightful presentations that deepened my understanding of Java and its ecosystem.
One of the highlights for me was getting introduced to the CMS world, especially the concept of Headless CMS, which was completely new to me.
Let's see about Headless CMS.

Why it's called “Headless”?

• The “head” is the front-end (like a website or app).
• “Headless” means the CMS doesn’t have a built-in front-end. It just provides content via APIs (usually REST or #GraphQL), and developers build the front-end separately.

Example:

This example will give you a clear understanding. It’s Like a Box of Content.

• You fill the box (headless CMS) with your articles, images, etc.
• Then your developer takes the content out and shows it however they want.

Usage difference between Traditional CMS and Headless CMS:

Use Traditional CMS when:

• You only need a website
• You want less coding
• You want to get started quickly

Use Headless CMS when:

• You want to build multiple platforms (app, website, etc.)
• You want more flexibility in design and code
• You have developers to build the front-end

How it Works:

• Content creators write/manage content in the CMS (text, images, etc.).
• The CMS exposes this content via an API.
• Front-end developers fetch the content and display it using any framework (React, Vue, Angular, mobile app, etc.).

Examples of Headless CMS:

• Contentful
• Strapi
• Sanity
• DatoCMS
• Prismic
• Hygraph (formerly GraphCMS)

That's it, guys. I hope I gave a basic clear explanation about Headless CMS. Thank you for reading my blog. Will see you in my next Blog.