I had an idea for this process, which I saw on another community-run knowledge-base powered by Discourse a month or two ago:
Keep iterating the original post (as a wiki) and let new developers ask questions on it, whether clarifying or “where do I find?” questions. As those questions get triaged or updated (and/or inspire updates to the original-post wiki), they get moved to another thread (the “closed issues” thread) where people can trace back-conversation, following a link at the very end of the wiki. But the relatively short “issue tracker” thread remains a welcoming/manageable/less-intimidating starting point and tricks people (by being kept short) into writing a comment off the cuff, unencumbered by prior art
All joking aside, I think a periodic revamp here would be great and I’m happy to contribute in any way, but also trust @aschrijver to be the only process if that’s faster/simpler in this high-stakes context of creating a first impression welcoming new folks!
I just added some links and a subsection among the “Missing Pieces” (I held back from renaming it “Advanced Topics” because it includes lots of stuff that aren’t missing from AP but necessary for building a website with users…). Please ping me if I overstepped editorially!
@aschrijver, is the capability to move messages from one thread to another mod-only? Would “pruning” this megathread periodically be something make sense, since the original and first-followup are already so many pages long?
Think it is mod-only, yes. I don’t know whether pruning would serve to attract / focus people’s attention more on ongoing activity than just posting to the end of the megathread. Might experiment with what works best. @how can grant you mod here.
I added Hatsu to the list of projects that follow the best-practice to have FEDERATION.md in the root of their repository. If you know more projects that should be on this list, then please take a second to update the wiki (click the ‘Edit’ button at the bottom-right of the top post).
Ah thanks. That is much better location to consult. In that regard the guide in the top post isn’t really edited and maintained by anyone and likely getting outdated and link-rotted. I saw @deadsuperhero this morning give a call for feedback on developer documentation needs, as input for a docs website.
This forum is a do-ocracy and any initiatives like these are most welcome.