This session was held as a round-table discussion where people raised issues important to them, most of which surrounded making Drupal.org more easily accessible and identifying areas which were lacking in Drupal's documentation as a whole.

Feature requests
- Overview of how things connect (diagrams) -- Dale is attempting to spear-head this effort
- Screen casts/screen captures to provide visual explanation on how to accomplish tasks (Development Seed has offered to do work in this area)
- Improved search on Drupal.org (coming with 4.7 upgrade)
- Version control on documentation; better able to see what version of Drupal page corresponds to
- Ability to import/export documentation (Djun doing lots of work in this area)
- Ability to gauge how helpful pages are with some sort of ratings system as well as statistics analysis -- determine who has been helped by a page, who's finding what they need, who's not.
- Open up documentation process so people can easily contribute a quick note/correction here or there.
- Modularity of documentation to allow customization of Drupal docs for client installations, allow templating (for customization)
- Add ways of encouraging contributions... hall of fame, sponsor page, economic incentives
- Teasing apart drupal.org into separate sites for developers, themes, support, usergroups?

Areas for improvement
- Better explanation/overview for how theming works; we are currently turning off designers by making things too technical
- Lack of editorial vision; there is lots of content coming in every day, but it seems hap-hazard; brittleness of information architecture
- Should there be a separate site for newbies? (lots of agreement on this point, but it carries its share of cons)
- The term 'Handbook' is not immediately recognizable as support documentation. Suggestions were to rename this tab to something like "Documentation"
- Simplify the "Support" tab. Wayyy too many links here.
- Navigation is difficult; more links directly to deep into the handbook to key areas of interest
- There is 'friction' within the documentation working group, which can make potential contributors intimidated or annoyed
- A FAQ: Compile list of questions in the forums/mailing lists that are asked all the time in one place
- A 'tour' or 'start here' document
- Improve Drupal.org homepage? "River of News" is not seen as attractive. Not obvious for people to know where they should go when they first arrive.
- Hard to get a sense of how the project and contributing to it work... where do you start?
- Have checklist of goals that can be viewed 'at a glance' to see where progress has been made in the documentation, what else is left to do, and where people can help out (issue tracker is not good for this; most people who contribute documentation are not developers so working with the concept of 'bugs' is foreign)
- have division between writers/subject matter experts; team up people who can write with people who know what needs to get written
- Right now, the site has a very internal view rather than external view (data centered, not user centered). Need to define target audience for each section and then always write toward that target audience. There are many ways to break down target audience:
- skill/familiarity
- task orientation
- background
- role
- type of site they're trying to develop