Why I made my own headless CMS

I'm back!

I’m juggling several projects right now. A mindfulness app, an interview-prep product and other internal projects that are not so visible right now. Each has its own site and blog, either built with Meteor, Gatsby or Vite or hosted on hashnode, such as this blog. Each has its own social accounts. The fragmentation is creating drag and honestly making me not want to post at all.

I need a single place where I write something once and decide when it goes live. When the publish moment arrives, the right blog should update instantly. From the same source text, I want quick derivatives for Twitter and LinkedIn so I’m not rewriting the same idea three times or jumping between dashboards.

The goal is a unified system that removes friction from publishing across my portfolio. One workflow, predictable outcomes, less cognitive load. I'm quite pleased with the progress so far. I already hooked it up to Răgaz and LeetTrivia's blogs, and now I successfully made it the single source of truth for this hashnode blog.

I will share more as the project matures and I add new blogs and perhaps platforms in the mix.