I just wrote a big ol' blog post about indiewebifying my event discovery and RSVPs. Thinking about it just now, however, it's a bit of a mish-mash between why I wanted to do it, and how I did it.
For someone coming to the post who is new to the IndieWeb, it's probably bit off-putting (and maybe fuel for the fire of 'IndieWeb is too complicated'). And for someone who already knows about the IndieWeb, but isn't using WordPress, they might skip over the hows and in the process miss some of the whys.
So in future I might try and split these kinds of articles into two - a 'why' post, and a 'how I did it' post. The 'why' post will kind of be my behaviour-driven development specs, so to speak, and probably mostly links to various pattern pages on the IndieWeb wiki. And the 'how' post will get into the weeds of one very specific implementation, liberally referring back to the 'why' post.
I think that would work well and make the articles a bit more reusable and less niche.
Been doing a small bit of wiki gardening on my books pages today. Nothing major, just starting to link the different ideas from different books to the concepts they're discussing.
I really like how Nadia Eghbal's writings are peppered with cultural references. When I'm getting to the point where I'm writing longer-form articles on an idea, I would like them to have a similar cross-pollination vibe. Like Mark Fisher, too.
Though I would still want my own curated paths in addition to this generated map o' everything.
4 Watched Making Connections in your Notes
Fairly high-level intro to org-roam, and why you might want to use it instead of Roam (and also why you might not).
The Roam approach to note-taking is to start with your daily page, and then link to things from there. This makes a lot of sense to me, and fits in with my current process for the blog and wiki combo.
You just start with whatever is currently on your mind, and that goes in the stream, but links out to things in the wiki. I tend to copy it into the wiki at the same time, too, if it makes sense. Probably one thing to think about though is what in the stream do I want to be public versus private - that would change the workflow a bit.