Submitted by jhodgdon on 8 September 2011 - 1:58pm
At DrupalCon London a couple of weeks ago, I was approached by several developers who wanted to do projects that would help the Drupal Documentation team. I had a few thoughts then, but now I have something more organized... If you are a Drupal site builder or a Drupal/PHP programmer, the Documentation team needs your help with the tasks listed here: http://groups.drupal.org/node/174499
At local Drupal group meetings I've been to lately, the big question among those of us who build sites with Drupal is (as you might guess): Is it time to switch to Drupal 7? I can't give you a simple yes or no answer to this question -- I think it depends on your situation, mainly due to the state of contributed modules and some key core bugs -- how disappointing!
There's a lot of energy right now in the Drupal Documentation Team, which is great! My docs team co-lead Ariane has put together a team of dedicated folks who are regularly contributing to the Drupal.org on-line documentation, and their efforts are really paying off in better documentation.
But there isn't quite so much energy in the API/programmer section of the docs team, which I'm in charge of, so I'd like to make a Call to Action. What I'd like to have on the Docs Team:
Most of the clients I set up Drupal web sites for are not experts at hand-editing HTML, and prefer to use a WYSIWYG (What You See Is What You Get) or Rich Text editor to create their content. I generally set them up with the WYSIWYG API module, and use the FCK Editor or CK Editor plugin. Over the couple of years I have been using this module, I've learned a few configuration tricks, so I thought I'd share them here.
The Seattle Drupal User Group put on a free Drupal workshop for beginners in October of 2009, called the "Seattle Drupal Clinic". I now have a web site up at poplarclass.com that contains the agenda, curriculum, planning spreadsheets, a "lessons learned" page, and other resources. If your group is planning a similar workshop, you might find it useful, and all of the information there has been placed in the public domain.
I just got back from DrupalCon San Francisco, which was a blast! I went to only two formal sessions, presented 1 "BOF" (informal) session, was a panelist for two panel sessions, and spent the rest of the time coding, reviewing patches, and meeting all the folks I already knew on-line from my work on the Drupal open-source project.
I recently agreed to take on two new roles in the Drupal open-source project: maintainer of the core Search module, and documentation volunteer coordinator, specifically for the in-code API documentation that's displayed on api.drupal.org.
I recently completed the process of adding SimpleTest tests to two modules that I maintain on drupal.org: Porter Stemmer (a module that adds linguistics-based matching of word forms to Drupal's core Search module, so that you can match "walk", "walking", "walks" etc.