The Big Headless CMS Lie
James Mikrut, a software developer, recently wrote an article exposing what he calls “The Big Headless CMS Lie.” In this article, Mikrut argues that the concept of headless CMSs is often oversold and misunderstood.
According to Mikrut, many companies are lured into the world of headless CMSs by promises of increased flexibility, scalability, and speed. However, in reality, he argues that these benefits often come at a cost. Mikrut claims that implementing a headless CMS can be complex and time-consuming, requiring a significant amount of technical expertise to set up and maintain.
Furthermore, Mikrut points out that headless CMSs can also lead to increased costs, as companies may need to invest in additional tools and resources to effectively manage and optimize their headless CMS. He also highlights the risk of fragmentation, as content creators may struggle to maintain consistency and coherence across different channels and platforms.
In conclusion, Mikrut urges companies to carefully consider whether a headless CMS is truly the right solution for their needs. He suggests evaluating the trade-offs and potential challenges associated with implementing a headless CMS, and advises companies to prioritize simplicity, ease of use, and consistency when choosing a CMS.
Overall, Mikrut’s article serves as a cautionary tale for companies considering a headless CMS solution, reminding them to think critically and strategically about their content management needs before making any decisions.
6:11
i heard " i just want some pu*sy 😂
About to recommend a headless solution to my company, payload is my top choice. Incredible work!
The CMS is never for the developer, but it can get in the way of the developer…
ofc he's a cs player
Since when Channing Tatum become a developer?
btw loved the presentation, James.
6:11 I'm pretty sure he said "I just want some pussy"
it sounds like a traditional CMS for next js folks
I hate webpage more than a wart that screams only on hot dates
I started to learn code 1 year ago. I’m stop trying to get past the cli errors. Maybe one day I’ll start to write code instead of being shunned by it.
100% windows for CS Go. I'd have a beer with this guy
6:51 “if you don’t even build with an API” — exactly — What year is it? … Asking a hypothetical question on stage of a service paddling server-client rendering and coupling like its the 1990s PHP again.
I want this!!!! DO IT
It’s hard to take someone seriously when he claims “I’ll say everything to get money”
I think Nuxt does all this already
I stopped listening after I heard: "I would say anything to make money".
serverless ✌️⭐️
Thank you. I thought im only one who struggled with deploy
a few hundreds Ks of JS is actually a big thing, most web pages don't serve a 10 MB video, the tech should scale from simple static content to complex UI or big content, a simple page should not load and parse big scripts if it's not necessary, it should be mostly static and use very few CPU resources.
You should look up TinaCMS, has all of this except its git based, but still awesome
People peddling headless cms tryna tell people the whole thing going to have to go through a build step to see your content updates 😂 and then the build fails 😂