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.

Separation of article concerns

2 thoughts on “Separation of article concerns”

  1. In reply to https://doubleloop.net/2020/04/04/separation-of-article-concerns/.
    A fair share of my blog posts suffer from this—I think. I often feel they’re of no use at all to those already in the know, and completely incomprehensible to anyone else.
    That said, I’m doing this mostly for myself, and I’m at least trying to share whatever it is I’ve been messing with.
    And while I sort of write technical documents for a living, I have a hard time reading—and writing—extensive blog posts that want to cover everything.

Leave a Reply

Your email address will not be published. Required fields are marked *