Documentation Structure - Core Modules and Contributed Modules

I was just reading the "Handbook update -reorganization progress" news

Where I discovered that a page listing contributed modules exists here:

I think I'm reasonably thorough when I search for information on this website, and yet this was one of those too familiar, "how did I miss that page" moments I frequently have trying to find information on Drupal.

It seems the most direct route from the Contents of the handbook to "Contribute Modules" page is:

Handbooks -> Installation and configuration (section) -> Drupal modules and features -> Then read the second paragraph on this page to find the link to -> contributed modules page


Handbooks -> Installation and configuration (section) -> Drupal modules and features -> Then scroll to the bottom of the list of modules to find a link to -> contributed modules page

I think the "Contributed modules" page is top level stuff that would be more useful on the Table of Contents under the Installation and configuation section. When I had just begun reading about Drupal, it would have more quickly helped me to understand the distinction between core and contributed modules to see the two categories listed sequentially in the table of contents. As a newer user to Drupal I think the following would have been the most helpful way for me to originally find information about modules.

cvs: interesting modules

I just discovered that there are many (60, 100?) interesting modules in the cvs repository that are not listed anywhere else, as far as I know. For example, there is a

friendlist module (2004)
and an epublish module

ecommerce modules: list

this link lists ecommerce modules, as well as you can help write documentation for it!

here is the link for how to write documentation for modules

thanks to amazon for pointing this out.


if you volunteer for a module, just make a comment here. I started doing paypal subscriptions and I'll see if I can understand it enough to write something up.

add documentation? paid membership comments

Here is an example of what I think I would a useful addition to the documentation. Many many thanks to sepeck who has taken on the immense job of overseeing and reorganizing the documentation.

Some threads about where users can create unofficial documentation

Every time I have a question I spend hours reading the forums and pulling out the best answers. (The answers often conflict.) I'm sure others do too. It seems to me it'd be useful to add our summaries to the documentation. Particularly for the contributed modules. Is it possible to create a space on the created modules where people can leave comments that would be unofficial documentation? Otherwise, every time I research a module I read the forums, the bug reports, and every user has to do this again.

how to create paid membership using Drupal
summary written Jan. 11, 2006

The 2 main modules mentioned are:

ecommerce module

paypal subscriptions module
March 2005

Here is a list of key threads I pulled out, listed in the order of the search results (out of about 30 I read)

22996 module author did not reply. may not be supported
43609 can't edit or delete subscription
14434 Dries favors having a good paypal module

A suggestion to make the handbooks searchable

I don't know if it is possible or practical, but I learned long ago that the way to get relevant search results on Drupal is to use Google site search.

If handbook paged were aliased to /handbooks/* then you could search using google and get only matching handbook pages and skip old forum topics referring to version 4.1 techniques, etc.

sample glossary page for newcomers

Here is a sample glossary page. Where would be a good place to put this? This is related to the thread I started about documenting comments. Please see While these terms are not frequently asked questions, they do cause confusion for the newcomer.

Here are some terms and acronyms that are not Drupal terms that are used on this site that a newcomer might not know.


Intergrated Development Environment. Used here in relationship to debuggers.


Subscribe with RSS Subscribe to RSS - Deprecated - Documentation