Last updated April 27, 2012.
On this page, your friendly Documentation team leader(s) will try to keep you up-to-date about what the current priorities are for contributing to the documentation of Drupal, or how to find them if they are listed elsewhere.
Notes:
- New contributors: If you are new to Drupal or new to contributing to Drupal documentation, the priorities listed here will probably not be the best place for you to start. Instead, please check out the New Contributors Tasks section.
- Check the How to Contribute to Documentation pages for other ideas on how to contribute, guidance on style, instructions on how to contribute to any of the efforts below, etc. -- this page is just meant to be a list of our immediate priorities.
- You may also be interested in reading the recent documentation team update posts, which you can find by scrolling through the Drupal News archive, and our group discussions, which you can find on http://groups.drupal.org/documentation-team.
Sprints
The Documentation Team page on groups.drupal.org is the place to go to find out about our current documentation "sprints"! Sprints are specific priorities to work on for specific time frames (if we have some...) -- join us!
Infrastructure and Process
The Documentation Team is discussing and working on several infrastructure projects (i.e., projects aimed at improving the tools and processes we use to create and edit Drupal documentation). Stay updated about these types of projects at:
- Documentation Team page on groups.drupal.org
- Queue of issues tagged with "docs infrastructure"
- Documentation Planning section of the Community Initiatives pages.
Here are some current projects that are looking for developers who can take them on:
#1508832: Support +/- expand/contract in Book navigation on Drupal.org
#1283496: Help/Docs system: editorial/translation workflow and permissions
API docs cleanup
The programmer segment of the Drupal Docs team has been working on cleaning up the Drupal 7 and 8 API docs (those are the documentation of PHP functions embedded in the Drupal Core code). We've made a lot of progress, but more help with creating and reviewing patches is always welcome! Here's the issue, if you want to join in (instructions there):
#1310084: [meta] API documentation cleanup sprint
Community Documentation updates needed
We need to make sure that the essential sections of the Community Documentation are updated for Drupal 7. There is a d7docs issue tag to help track Drupal 7-specific issues we need to keep up on. Some specific areas to focus on are listed in the sections below.
Mostly done
- Core module handbook pages: In progress on final reviews on the core module pages for modules that were already in core and filing new issues in the Documentation queue for any larger problems.
Needs work!
- Theming guide: Theme guide updates for Drupal 7 and restructuring are in-progress. Any existing pages should have any information unique to Drupal 7 added to them, and we may need to add a few new pages for any completely new functionality. (See issues #740194: Update theming guide for Drupal 7 and #1146010: What would an “ideal” theme guide look like? if you want to help out!)
- Module developers guide: Developing Drupal 7 modules is fairly similar to developing Drupal 6 modules. However, a lot of the hooks have changed, and several core APIs have been completely overhauled. The guides for some of the APIs have been updated for Drupal 7 (notably, the completely-redone Database API), but there is still work to be done. You can help by:
- Reviewing the API and Module developer's guides: We need help reviewing the Drupal API guide and the Module developer's guide to see if there are places that need updating. There is a start to this review on issue #1001760: Review D7 module developer documentation, so please check there first to avoid duplicating the review effort. If you find areas that need to be updated, please file new specific issues in the Documentation project, similar to #1001754: Drupal 7 File API doc is incomplete. Tag the issues “d7docs" and “developer".
- Updating the API and Module developer's guides: Updating areas in the API guide and Module developer's guide that have had issues filed noting they are out of date or incorrect. You can find these issues by searching for issues tagged “d7docs" and “developer" in the Documentation issue queue.
- General API issues: There are also some API documentation issues in the Drupal core issue queue that could be worked on, but these are mostly a lower priority than the areas noted above. You can find these issues by searching the Drupal core issue queue for open 7.x or 8.x issues that are either in the “documentation" component, or tagged with “Needs Documentation".
- Coder routines: This is not exactly a documentation issue, but the Coder project needs help writing routines that will help module developers upgrade from Drupal 6 to Drupal 7. If you are a coder, you can help with that by searching the Coder issue queue for component Upgrade Routines, finding an issue, and submitting a patch.