Dogfooding: Why I Migrated My Own Blog to Writizzy

In 2022, I created an open-source static blog generator: Bloggrify.

It’s conceptually similar to Hugo—it generates a static site (just a bunch of HTML files) that you can host for free on Cloudflare, GitHub Pages, or Bunny.net.

Before that, I had tried everything: WordPress, Joomla, Medium. I wanted to regain flexibility and customize my blog exactly how I wanted. But let’s be honest: I’m a developer, and I mainly wanted a new technical playground.

Fast forward to 2026, and I have to admit: using a static blog has become a major friction point for my writing. So, I decided to migrate again, this time to a managed platform: Writizzy, another product I’m building.

This move is a great opportunity to talk about several things:

• Dogfooding: Why you absolutely must use your own products.
• The harsh reality of Open Source: Why it’s harder than it looks.
• Product Satisfaction: The joy of building something people actually use.
• The future of my projects: Bloggrify, Writizzy, and Hakanai.io.

Bloggrify: When my blog was a technical playground

Bloggrify started as a love letter to the Nuxt ecosystem, specifically nuxt-content. Back when I migrated from WordPress, my criteria were simple:

• A simple templating language (Markdown).
• Extensibility (RSS feeds, sitemaps, etc.).
• Low cost.
• Low carbon footprint (static sites are incredibly efficient).

In 2022, it wasn't a "product" yet—just my personal blog code made public. It only became a full-fledged open-source project in 2024, with a dedicated site and a proper README to encourage contributions.

I wanted the product to be "opinionated." Nuxt-content does 90% of the heavy lifting, but it’s a generic tool. For a real blog, you still need to build the RSS feed, sitemap, robots.txt, comments, table of contents, share buttons, newsletter integration, analytics, and SEO.

That’s what Bloggrify is: a "starter pack" that comes with everything pre-configured. Think of it as Docus, but for blogs instead of documentation.

The Reality Check: GitHub Stars vs. Actual Users

I’m a numbers person. When I launch a project, I want to see usage. It might sound trivial, but considering the effort it takes to manage NPM releases (which is honestly a nightmare), handle versioning, and maintain themes, you expect a minimum return on investment.

Bloggrify reached 164 stars on GitHub and sits somewhere in the middle of the pack on Jamstack.org. That’s... okay, I guess.

But in reality, I have almost zero feedback on its actual usage. A few rare GitHub issues, one contributor who was active for a few weeks before vanishing, and then silence. I only know of one blog that used it before switching back to Hugo.

The experience has been bittersweet. Building in the dark is demotivating. However, it did lead me to launch two other side-products:

• broadcast.hakanai.io: A newsletter system for static blogs based on RSS feeds.
• pulse.hakanai.io: A specialized analytics tool for bloggers (not just generic web traffic).

Transitioning to SaaS

I launched Broadcast and Pulse in 2024 and 2025. They’re living a quiet life, but they aren't "exploding." My target audience is static bloggers—mostly developers. And as we know, developers are the hardest group to convince to pay for a service!

Still, I’m satisfied. These products taught me how to build a SaaS, handle subscriptions, and find my ideal tech stack. My own newsletters were sent via Broadcast (reaching about 150 subscribers), and I used Pulse to track which articles were actually being read.

The reality? These two tools generate about €100 in Monthly Recurring Revenue (MRR). Not enough to retire on, but a great learning experience.

And that brings us to Writizzy.

Enter Writizzy

With Bloggrify, I realized my writing workflow had become painful. Between maintaining the framework, jumping between spell-checkers, writing in Markdown, spinning up a local server to check for broken links, and waiting for build/deployment times... I was losing hours.

For my last article, someone pointed out a few typos. It took me 20 minutes between editing the file and seeing the fix live. Add to that the friction of managing images in an IDE and the recent Nuxt 4 / Nuxt-content updates which, while I love them, have made the dev experience slightly slower for simple blogging.

To be honest, I wasn't aware of that. I put up with these inconveniences and was still very happy to have “flexibility” in what I could do with my blog. I wasn't fully aware of this "friction" until I built Writizzy.

Writizzy is the synthesis of my blogging experience. It’s a mix of Substack, Ghost, and Medium, but built as a European alternative with four core pillars:

1. Sustainability: Focusing on reversibility and interoperability.
2. Discoverability.
3. Economic accessibility: Implementing Purchasing Power Parity (PPP).
4. Transparency.

I moved my English blog to Writizzy first (this one), with no intention of moving the french one. But I soon noticed I was writing much faster on the English site. The workflow was just... better. Copy-pasting images directly into the editor, instant previews, no server to launch. It was a joy.

The Future of My Projects

I hesitated for a long time before migrating eventuallycoding.com. I knew that by doing so, I was taking the risk of killing Bloggrify. If even I don't use it anymore, the project enters a danger zone. When you don’t use your own product daily—when you’re no longer obsessed with the problem it solves—it’s almost impossible to stay attached to it.

This is a symptom I see in so many "disposable" projects across the internet: built by people who flutter from one idea to the next without any real skin in the game. So yes, moving away from Bloggrify is a risk.

But I’ve come to terms with it. Today, I have almost zero evidence that Bloggrify is being used. Meanwhile, Writizzy already has 314 blogs and 11 paying users (€135 MRR) in just four months. Why stubbornly cling to Bloggrify? Ultimately, I believe I’m solving the same problem with Writizzy, but in a much better way.

I receive feedback emails and feature requests every single week. I get constant positive reinforcement from people actually using it. The product isn’t perfect, but it improves every day. It improves because real users are pushing me to refine the site, fix what’s broken, and add the features that absolutely need to be there.

And it also improves because I use it constantly. This is the massive benefit of dogfooding. Every day, I am confronted with my own software, so I know exactly what needs to change.

So yes, Bloggrify is moving to maintenance mode. I’m taking this opportunity to turn all templates into Open Source. Two of them were "premium," but it wouldn't make sense to keep them that way today. I tell myself I’ll still evolve it from time to time, but honestly, I wonder if I’m just lying to myself.

As for Hakanai.io, I’m definitely continuing. The problem it solves still fascinates me. I get great feedback, especially on Broadcast. Pulse, however, suffers from being misunderstood. It’s a "blog analytics" product, and people don't really grasp what that entails—SEO advice, outlier detection, evergreen content tracking. I’m not great at marketing, so it mostly flies under the radar except for the readers of this blog who took the time to test it. But I’m motivated to keep them alive.

As for Writizzy, there is no doubt. The product is incredibly exciting to build. The stakes are high: building a platform for expression that exists outside the US-centric giants. The traction is there, and the numbers follow (+45% MoM user growth).

Welcome to this blog, now officially on Writizzy. As a reader, you can already test several things:

• The comments section.
• The newsletter subscription (if you haven’t already).

The Discover feed to read other articles from Writizzy bloggers. We’ve handpicked a few to start with, and this feed will become even more customizable in the future.

Welcome home.