has put forward several key comments and questions that can guide us, most of them pointing to this big question: Is the book really useful? I imagine a workflow sort of like clearing out a garage.
When was the last time I used these... Ski boots? Chainsaws? Baskets of children's toys? Etc.
also has a profound vision for how to make the process accessible for more people, which I think is equally important and complementary.
Another related thing: by now it is beyond cliche, but many companies in the tech and online industries are interested in hiring people who are familiar with "Agile methods". I think we already follow many of the basic ideas of the "Agile Manifesto". I don't think we should be pedantic about it, but maybe it would be helpful to upgrade our workflow with some agile magic. That way, if any of us are ever looking for jobs ☞☞ in the tech industry (ahem) then we can say "Agile spoken here." I think will testify to the relevance of this...
So, a thought: one Agile-esque idea that we could use to connect some of these ideas is the notion of a User Story, which is, again, hardly cutting edge. Related magic sauce is something called "Behavior Driven Development". https://en.wikipedia.org/wiki/Behavior-driven_development This is a very software-oriented kind of idea, but I think we could use a variant of it for the book.
Finally, for those who didn't see it yet, peeragogy.org is now redirecting to peeragogy.github.io which has implications for the practical day to day workflow (but maybe not much else). More soon?