Seeking co-maintainer(s)

Ever design a site and happen on a nifty trick that you may want to use again? You wrote it down and lost the paper, didn't you.

Why Do I Need It?

Unfortunately Drupal does not include the powers of immortality or invincibility. You may someday get hit by a truck, or even just decide that you no longer want to maintain the site. So someone else may have to take over.

Where do they start? I know you documented the site really well, but the next person doesn't want to read those 14 binders of documentation you left behind. They can always go through all the administration screens and look for the information, but that can take a lot of time and even those pages don't tell you everything. Some things you're only going to get by looking directly into the database.

This is what the Site Documentation module is designed to do. In addition, it will detect some problems that may exist in your installation, and optionally correct some of them.

Content Access allows you to manage permissions for content types by role and author. It allows you to specify custom view, edit and delete permissions for each content type. Optionally you can enable per content access settings, so you can customize the access for each content node.

Ever want to add help text to a form in Drupal? Don't like a field title chosen by the developer? Want to change the description of a form field?

Upgrades the version of jQuery in Drupal core to a newer version of jQuery.

This module provides a "colorpicker" form element for CCK forms, and also for module developers to utilize.