>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #67367. --> Reported by: [webchick](https://www.drupal.org/user/24967) >>> <p>Djun Kim and I had coffee the other day and were kind of reminiscing about the Vancouver documentation session and some of the items that came out of that. Other people have mentioned before the "digg vs. slashdot" factor, and I think we all generally agree that we need to reduce barriers as much as possible for people to update documentation.</p> <p>The system for the handbook we have now, quite frankly, kind of stinks. While it's arguably harder for people to put spam/garbage in the handbook (people can add pages about viagra willy-nilly but they're placed in the moderation queue first), it also is harder for "normal, do-gooder" people to submit/correct documentation. New pages can sit in the moderation queue for days (or longer) before someone gets a chance to approve them, module developers need to contact members of the site admin team to update <strong>their own documentation</strong> in the handbook, and the only way for Joe Random who discovers a typo in the text to fix it is to create a documentation "bug" rather than just edit the text directly. The concept of using "bugs" to track documentation problems is totally counter-intuitive to people who have skills in writing and editing but not coding (and some great writers fall into this category), and it also turns what would be a "few seconds" fix into more like "few minutes" fix which doesn't actually get fixed, but instead sits in a queue until someone has a chance to take a look at it, hours or days down the road.</p> <p>In short, there are a lot of barriers in front of people who want to help improve the handbook documentation, and removing those barriers is necessary if we want the documentation to truly shine.</p> <p>One idea is to move the handbook to a completely separate domain, such as docs.drupal.org and point the Handbook link over there. We'd hand 'administer nodes' privileges out to either everyone, or just authenticated users. Site admins get "administer users" privileges and can handle banning people who want to try and abuse these privileges. This would also allow us to install additional modules such as <a href="http://drupal.org/node/9838">Markdown with SmartyPants</a> to make documentation editing easier, or <a href="http://drupal.org/node/39121">Export DXML</a> to allow other sites to pull the handbook pages for themselves, without worrying about the performance/security(?) implications for the main Drupal.org site. If I'm trusted enough (and it is totally fine if I am not), <strong>I would volunteer for putting this together</strong>.</p> <p>If we want to keep everything at Drupal.org, that also works. We have a new permission in 4.7 of "edit book pages" which is like "administer nodes" except only for books. Just dole that out to all authenticated users and bang, you're done. </p> <p>"Edit book pages" permission to all authenticated users still too risky? How about this? I code up a module or patch for book module (or maybe actions/workflow could work for this??) so that upon creating a new handbook page that gets moved out of moderation queue by a site admin, you are added to a "documentation team" role that has "edit book" privileges.</p> <p>One way or the other though, we really need to fix this. Those are some suggestions, anyone else have any others?</p>