I'd suggest a smaller scope, as writing for a whole year can be a bit of a daunting task.

I second this. Small chunks is easier than one massive thing all at once.

I also have the habit of keeping a `~/notes.md` file, which I can access at the drop of a hat with a shell shortcut (I use fish, so I have the function `nn` which calls `$EDITOR ~/notes.md`). If you use multiple computers, which I do, you can use a common git repo with a branch for each computer as a backup. I generally end up writing a few notes every day, which means if I want to publish something in the future I have good source material to use.

Apologies if this post was a bit self centered, I hope my sharing my methods might be useful :)

> I also have the habit of keeping a `~/notes.md` file

Oh, I did spin up a Honk instance to keep notes on "things-i-did". It ... does not have many posts (83 since 2022-05). Ironically it doesn't have "set up honk instance for note-taking" in there.

But the `notes.md`+`git` idea might work. Although I know the first time I get a conflict on the `pull`, it'll all fall down...

Agreed. I find for myself, for a blog post that is about something else I've done, the ideal length is about 5 paragraphs and it should take no more than an hour to write. Longer than that and it just doesn't get done, or it should be considered a project unto itself and should be managed as such with dedicated time set aside for it. Writing about everything I did in year would be a lot longer than 5 paragraphs, which means I need to break the concept down (perhaps into months, or write something per-project instead).