Documentation for the documenters
I see a general issue with Crabgrass: there are gaps in the documentation, but how can those gaps be filled by someone other than the programmers supporting Crabgrass? (Who should be spending their time coding, for the most part.)
I'm new to Crabgrass and am excited that it exists. I'm a pretty good writer and would be happy to write documentation. I do some programming (mainly statistical scripts in R) but don't feel up to hacking on the Crabgrass code routinely. I'm willing to wade through technical details and ask technical questions of those who know, in order to construct a concise guide for others. But how can I myself learn? For example, is there somewhere a detailed description that I could read, and follow up with questions?
Is this sort of question appropriate in the issue tracker?