New initiative

In case you didn't notice, the Drupal Association has made a list of 6 priorities for 2012. Number 6 is "Make Drupal.org awesome for site builders", and Documentation is a large component of this.

So I just thought I'd make sure the Documentation Team was aware of this discussion:
Original page discussing the 2012 priorities: http://groups.drupal.org/node/197558
Sub-page specifically about this priority: http://groups.drupal.org/node/198708
Association group home page (which also lists these priorities): http://groups.drupal.org/drupal-association

I've been asked to edit the Standard Issue Tags for Drupal core page to correct its characterization of accessibility issues, and, as usual, the editorial eye found more needing to be fixed than it was asked to review.

Specifically in this case, there are cases in which two issue tags are difficult to distinguish from each other. "Accessibility" and "needs accessibility review" is one such instance. Another is "usability" and "needs usability review." The definitions given for these terms don't help clear things up, either.

Before I make sweeping changes, I would like to get feedback from folks who are familiar with the issue queue about a role- and intent-based approach for telling who should — or, sometimes, who may — use any particular tag.

Hello everyone,

I've just had a debate on the issue queue for core about Fast 404s and how to route around the issue of having Drupal be the 404 handler by default. The debate was enlightening for everyone involved I think. But the consequence should be a documentation page addressing the issue and the multiples available strategies for solving it.

Here is a proof of concept I was trying out this morning.
I wanted to read the SimpleTest documentation on my (non-internet connected) ereader so I made an ePub document out of the all the web pages. This centralizes the content into an (almost real) book that can be read on most electronic readers (with working Table Of Contents, embedded images, etc).

Due to the file upload restrictions (it doesn't recognize the '.epub' extension), you must change the '.html' to '.epub' after you download it, in order to read it.

Hey all -

DrupalCon Chicago's Core Conversation proposals need to be in by next Friday. Jennifer (jhodgdon) and I have been pondering whether and what might make a good topic or two to pitch.

Please post with ideas and whether you'd be interested in attending a docs focused session, it'll help us gear our proposal towards something everyone will be interested in!

Thanks!

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.

Greetings, Documentation Team!

Just wanted to raise to your attention that Google is sponsoring a program to help 13-18 year olds get involved in open source called Google Code-In:http://code.google.com/opensource/gci/2010-11/index.html. The program runs Nov. 22 - January 10, and the past incarnation (GHOP) netted us rockstars such as Jimmy Berry (who wrote the infrastructure for our automated testing bot), Daniel Wehner (who is now a Views co-maintainer), and Charlie Gordon (who has done a bunch of work in core on SimpleTest and D7UX patches).