Using a **headless CMS** for your developer blog is **bullshit**. Let me explain why.

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

A headless CMS is not suitable for a developer blog due to unnecessary overhead and lack of flexibility. Markdown is suggested as a simpler and more efficient solution.

A Headless CMS is Bullshit for your developer blog

Where does it make sense to use a headless CMS?

Why is it bullshit for your developer blog?

Though it’s technically headless, I’m putting my blog posts on Notion and pull them via Notion API when compiling to static contents on nextjs. This way I can write and publish whenever I want without having to get to my computer to do stuff. YMMV.

The question is how much does a headless solution cost

I do agree that headless is a bit overhyped. Nor once nor twice I was reading articles that headless will solve all of my problems - speed, ease of building etc. Truth is - headless is not for everyone and it doesn’t fit every usecase.
I do agree with the author that in most cases using a headless CMS for a simple blog is too much. On the other hand I see the urge of having a headless CMS and just changing the front-end from time to time.