Let's rewrite the OS while we're at it since that's in the spirit of programming! :) Just use the nice tools available unless your goal is to rebuild the stack.

Or if you can find one that's close to your exact needs, use that and submit patches and pull requests upstream, or fork and maintain your fork if your changes aren't appropriate or acceptable for upstream. Easier than rolling your own if you just don't feel like going to that extreme, and still helps the ecosystem grow and thrive.

Assuming that the purpose of the blog is to write/publish, then all of that is distraction from actually writing.

Blogging about creating a custom static site generator for the blog is the most common first (and last) post.

If you do it for the love of the game, definitely. It's a fun little project.

I rolled my own because I wanted to use Jinja inside Markdown. This lets me include widgets in the content, and use Python-based constants in the text. For example, when the German minimum wage changes, I change one constant and it triggers a bunch of updates across the website.

I also wanted to control the content-to-website pipeline a little better. The SSG builds pages, but also generates text-to-speech audio for glossary terms, makes some typographic changes, and lints the Markdown for site-specific issues.

I wrote a bit about it here: https://nicolasbouliane.com/projects/ursus

The code is here: https://github.com/All-About-Berlin/ursus/