Documentation

I just finished updating http://drupal.org/upgrade this page just basically explains what a update / upgrade is, and links to other pages. I then found http://drupal.org/node/548922 which is very similar. I'm not sure if /upgrade is now complete or still needs work. How does someone know if it's complete? I personally think the links off of it are not in the best order or work quite right but I didn't know what the focus or intent of the page or links were. Personally I'd like to see the text of the update.txt posted. Why make someone open that file?

In Drupal development we have "core", which is carefully tended by a strong, collaborative community, and "contrib", which is pretty much wild west and has extremely low barriers to entry.

I propose that we do the same thing with the handbook.

<

ul>

Hey fellow docs enthusiasts!

As some of you may have seen, there is going to be a big Docs Sprint in Vancouver in December (come join us if you're nearby!) The other part of what's going on that weekend, is that the core Docs Team members traveling here, as well as a few core devs (webchick, chx, and dmitrig01) will be gathering on Friday to discuss the Docs Team structure and initiatives in a dedicated retreat style afternoon.

We'll be discussing and brainstorming about things like:

I recently got the opportunity to work on an idea that I've had for a few weeks – some kind of automized technical documentation of Drupal sites. It resulted in a rudimentary but working module Documentation Robot, collecting some technical information about the site where it is installed and summarizing it on a page.

It currently collects information about node types (including CCK fields), installed modules/projects, and user roles. In the pipe is also support for documenting views, panels, better CCK field documentation, and a tonne of other ideas I got. I also want to make the collected information re-usable in a number of different formats (for example DITA or creation of book nodes), but that is further off in the future.

After a big discussion with some of the core devs who attended the PNW Drupal Summit last weekend, I've created a page for people who don't consider themselves part of the Docs Team to sign up as willing to mentor people working on Docs. http://drupal.org/node/936522

The idea is that people working on docs often need help with technical details of what they're documenting, and don't know who they can ask. The people I was talking to were more than willing to help out, and we also talked about pairing up docs people with contrib maintainers so they can help maintain project-specific docs.

Can anyone help out on D7 Theme docs? There is a big need for help there, and it's an area I am totally clueless about. 2 issues on my radar:

• http://drupal.org/node/755826 (re: core theme section of handbook)
• http://drupal.org/node/740194 (re: updating theme guide)

I think it needs a lot of love, so if anyone can adopt these and help out, that'd be fantastic!

A ping in #drupal-docs earlier has brought to my attention that the Docs style guide only applies to handbook and not explicitly to interface text in Drupal core/contrib.

I'd think it should apply so we get consistent text and grammar formatting Drupal-wide, but didn't want to make such a sweeping declaration without some consensus from the community at large.