I completely agree -- as the docs have grown in size [] the organization has gotten worse. Originally I designed the structure to be similar to what you laid out, but things have gotten a bit out of control lately.
We're workin' on it, though, so if you'd like to help out I'd really appreciate it!
[] The length has nearly doubled in the last two years.
Thanks for clarifying things jacobian. :) I'd love to help out in a limited capacity (time constrained currently, unfortunately).
In the past I've submitted tickets via the Django ticketing system indicating errors/clarification/what-not for the docs, but almost every ticket got flagged as spam and didn't get submitted. I kinda gave up after that point. Any suggestions on how to get tickets submitted?
Oh, and one tiny feature request to the ticketing system: password reset. :)
Sorry about the spam filter. We get a shitton of spam (I think we're the largest Trac instance anywhere) and it makes the spam filter rather paranoid. If you're signed in it shouldn't get triggered.
I'm not sure how customizable Trac is, but one idea would be to implement reCAPTCHA for anything marked as spam (assuming robots are causing spam issues and not users). If it gets solved, it's probably a human entering something on the other end.
We've had that implemented since... I dunno, about six months ago maybe? (screenshot: https://skitch.com/jacobian/fgjmc/django). Not sure why you didn't see it. I wouldn't be surprised if Trac somehow didn't show it to you; it's a bit of a mystery to me some times.
We're workin' on it, though, so if you'd like to help out I'd really appreciate it!
[] The length has nearly doubled in the last two years.