You’ve probably seen the term “headless” used countlessly over and over again. There are so many platforms, services, and frameworks that use a hea...
For further actions, you may consider blocking this person and/or reporting abuse
Good analogy
Thank you!
Very simple explanation here. Love it!
Great explanation!
Thanks!
I imagine non-headless sites, like for example Shopify and Shopify themes, as a Nintendo Switch in this analogy. The storefront api of course is by shopify and is headless.
That’s another good analogy!
Too simplistic but nice term.
The best headlessCMS I have used is Directus directus.io/
I tried to use Strapi and followed many of their tutorials but never got a working product.
After playing with Directus I have one localhost installation for testing and playing around with the GUI.
I have another hosted on Supabase for additional testing and using a live API service.
And another fully hosted on DigitalOcean for my clients that allows them to make edits to their sites in real-time.
They deserve more credit for an amazing product. Strapi was a pain to even get started.
We have love for all open source projects! I’m sure both have good use cases in their own right
Thank you for the article, I liked the analogy. It would be cool to mention Nintendo switch as a not headless console :)
One question: what's the difference between the brand new headless architecture and the old and boring client-server architecture?
Yes the Nintendo Switch analogy is coming up a lot it’s sad I didn’t think of it while writing the article 😅
The headless architecture is usually created with abstraction and extendability in mind. This means that not only can it be presented by different types of clients (websites, mobile apps, etc…), but it also allows you to easily integrate your server with other services.
With traditional architectures everything is typically managed together on the same server as if it’s all a single module rather than separate modules. This means that when you need to integrate a new service or make changes to the server there are so many components that are dependent on one another that it can become a hassle or you’ll even need to do a lot of hacky solutions.
A headless architecture typically eliminates the need for hacky solutions because it’s designed to be a single component or module that can communicate with other components or modules, rather than having them all depend on one another.
Not sure if my answer is clear enough but I hope you found it helpful!
That's what I wanted to hear! Thank you! I keep on reading headless = "no front-end" and is not about that at all.
Also I think that is key that on a headless service, the service is a full product itself when on a client-server application both parts form a whole.
Thank you for your response.
The no frontend thing is just a part of it that explains the term “headless” but the entire architecture focuses on much more than that!
Thank you for your comments and for reading the article
It's not headless, it's just someone else's head.
Wait, what?
🤯
Thank you for the article. So client-server architecture is equal to headless architecture? Can we also called firebase as headless CMS?
Please refer to this comment:
dev.to/shahednasser/comment/1nbkj