I've been thinking about Rob's post and your notes on vHWC, and I agree that swapping the quiet writing hour for a question session makes a lot of sense. I've certainly learned a lot and look forward to the meetings.
One thing I'd like to suggest is a follow up on the idea of wiki pages for beginners. Someone was recently talking about a "for dummies" approach to setting up a web mention receiver, but from the context, I got the impression that they were dummies only about IndieWeb, not about PHP and servers and all the plumbing. Essentially Gen 1. A for dummies for that person would look very different to a for dummies for Gen 2 or Gen 3.
Would it be interesting if we picked a specific page and some of us (me, probably, although of course others too, and because it is a vHWC they could be anywhere) tried to do do a for Gen 2 dummies write up as a new version. Then at the vHWC you Gen 1people could take a look and explain in more detail, if necessary, or correct it, if wrong in some detail.
Does that sound worthwhile?
I don't actually have a good sense of which page might be best to start with, but it could be setting up to receive webmentions without, for now, going into the complexities of bridgy. So, for static sites, or CMSs like Grav.
Jeremy Cherfaspublished this
Personally I think that does sound worthwhile! But rewriting entire pages can be a little daunting. And I honestly wouldn’t be able to point you at a page that needs this done first, or tell you how to do it.
I will freely admit that I am not the target audience for these pages. That is what is keeping me back from authoring them as well, I don’t know the requirements. If you feel you have a better grasp of it (which you probably have) and are willing to put the time in: go for it! Knowing the Gen 1-people who usually show up to the virtual Homebrew Website Club I think everyone will be willing to take a look and comment.
I know what I would like to see as far as cleanups go, but as I often don’t manage my time well enough to go through with them myself I am hesitant to tell others to do it. Here are some examples of compartmentalisation that I found useful, and you may too:
For IndieAuth there are separate pages that go into detail for the authorization- and token-endpoints.
The Webmention article refers to a special developer page for people who want “to learn more about its technical details”.
And the Micropub page has proper subpages for collecting server and client implementations.
The Micropub page might be a prime example of a page that could be helped from more divvying up. There are a lot of code blocks with raw HTTP requests on there that may be better suited for a Webmention-style developer page. There is a little prior work on this already, as there is a separate page detailing the endpoint design.
Finally, I would be amiss to call out some other people who have started work towards a more accessible place: Calum’s Introducing the IndieWeb for which he would love it if people contributed guides, and Scott’s refresh session at IndieWeb Summit 2017 (and follow up session, and Figma sketch).
Martijn, Aug 20 2017 on licit.li