@ronguest You could fork the official repo and create a branch for something you’re thinking about, and others could fork that and collaborate, but it’s definitely not as easy as a wiki. With both Camino and NeoOffice, we/I used wikis extensively for drafting stuff collaboratively, and I agree that kind of workflow works great. Particularly when I don’t have a big block of time to fuss with VCS overhead, I could make some quick wiki edits and still accomplish something….
Actually—doesn’t github include a basic wiki with every repo? It seems like it does, although clicking that link does nothing in the help.micro.blog repo. Maybe @manton could enable the wiki there, or one of us could fork the repo and enable the wiki on our fork?