A few weeks ago I posted a draft Drupal documentation roadmap on Drupal.org. In that post I attached the full roadmap of goals, but focused on the first two we are tackling: a new information architecture (IA) and recognition/reward for documentation contributors. We had a meeting in IRC shortly after and we discussed a number of questions and ideas.
Too many times I have written a post, got it ready to go, set up my Twitter module to tell the world, and then right after I hit submit, I realize that I forgot to add the Twitter hashtags that will carry my tweet to glory. It occurred to me that maybe I should give myself a reminder by adding some hashtags to my Tweet by default, and the taxonomy terms I am using for the post are a pretty good bet for general usefulness. I whipped up a site-specific hack to do just that and thought others might be interested. It could probably be generalized so that it could be made a patch to Twitter module, but I'm not sure that is a great idea anyway and I don't have the time to even think it through, so have at.
Just one month from today I'm going to get three days of hanging out with brilliant folks from a number of open source projects to talk shop, brainstorm and generally have a great time. I'm heading to the Writing Open Source conference up in Canada from June 12-14. In the true spirit of open source, we're coming together to help each other out. The conference is about collaboration, learning, and getting stuff done. We all have a lot to gain and I hope that anyone who can get there, makes the effort.
I know that we have done the issue queue work as a challenge already, the very first one in January as a matter of fact. We got a lot accomplished in January, so let's do a spring cleanup. The reason I want to come back to the issue queue is two-fold. First, it still needs lots of love, as always, and second, I plan to finally post a beginning docs roadmap, and get some working groups kick-started around some of our big issues this month. We will be creating a lot of new issues in the docs issue queue, so I'd love for us to tidy up our work area before heading in to some ambitious new projects.
While I was at Drupalcamp Galway, Stéphane (scor) recorded an interview with me about not just the Galway doc sprint, but also about future doc sprints around the world. He's got the interview up on his blog and it's only 6 minutes long. Give it a listen and let me know about your Drupal event and how I can help you out.
I managed to get my hands on a pre-release version of a new Drupal book that just came out this week. The book is Front End Drupal and it is written by Emma Jane Hogbin and Konstantin Kaefer. The book says on the cover, Designing, Theming, Scripting, and I'm excited to see another book that really gets into Drupal 6 theming. When we, at Lullabot, wrote Using Drupal and we had to draw the line at a basic intro to theming, I was looking for a book to carry that forward. Since I am lucky enough to have myself a copy and found some time to sit down and read it, I thought I'd share my thoughts for those that may be trying to decide whether to order it (short answer is "yes").
We've been kicking butt with the doc challenges so far this year. Lots of work is getting done to clean up our handbooks. I really want to thank everyone who is chipping in, even if only for five minutes. Every little bit that we do makes it just that much better for everyone. This month's challenge will be an extension of a particular piece of March's style guide challenge; marking pages with correct vocabulary terms. One of the goals for the future of the documentation in the Drupal.org redesign is to use vocabulary terms to help people find what they need, rather than the only way to find something being to know the magic path through the book structure. To that end, we need to actually tag the pages.
In my post last week I mentioned that we had a professional cat herder, Cindy McCourt, for the Toronto Drupal documentation sprint and that the entire approach was a bit new and different for us. It was certainly different than anything I'd done before, especially in the Open Source or Drupal world. I should start by noting that all of this grew from community efforts by a number of people and isn't any kind of brainchild of mine. This sprint was an awesome showing of how Drupal contributors can do amazing things.