Skip to content

BlogΒΆ

Adding a blog to this site

This site now has a blog, and this is the first post on it. The short version: the knowledge base already records how it's evolving (the Log and the Git history), but nothing in there is a good entry point for humans to read what I did when and why (the story the log tells is informative, but not inspiring, if you will).

I realised this when struggling to note down how ponytail could interact with my opencode stack: it was a bit of research, and a proposal for a decision on what to do. However, I never did it, just because I did not need to or wanted to at that point in time. That turned it into a decision with draft status, the one on adopting ponytail, which I found quite unsatisfactory: it reads like a decision carried out and only the status in the rendered provenance card identified it as something that did not induce an action yet. I did not want to introduce a new actions category, because the result of a decision either lives in the knowledgebase as a guide or a blueprint, or is just a change in the world (as in: editing some config files on my machine, or installing something).

So, long story short: I wanted a place on this site to talk about the things in the knowledge base. I already have an about section sitting outside the knowledge bundle (hosted in docs/), which is more about guidance on how to interact with the site and knowledge bundle. A blog/ dir beside about/ and docs/ felt like a natural addition.

Technically, I'm using Material's blog plugin, together with a bit of magic in a hook to ensure the blog posts, the about, and the knowledge bundle all end up on the final site without interfering with each other (say, because a blog entry is not a concept, and must not be part of the okf checks, and the like). See also the tech stack page and the publishing stack.