Core Modules List suggested changes

The list of core modules at http://drupal.org/handbook/modules doesn't match the directory structure in the downloaded drupal-5.1.tar.gz.

Specifically:

1) "color" is included as a core module, but is not listed on the Core Modules page. Unlike other modules, this one is not inherently obvious, and it would be nice to have it documented here.

2) Neither "page" nor "story" have separate entries in the modules directory. I note that these two node types are included in the Default installation profile final hook, so I believe that they aren't technically separate modules, but are special circumstances node types. If that's the case, perhaps this should be clearly explained, the inclusion of them on the Core Modules page removed, and a better place found for explaining the exceptional node types Page and Story.

3) The core taxonomy module is listed here as "Categories (taxonomy)" which is extremely confusing--especially in light of the contributed module named "Category" (which is not compatible with all contributed modules, and can impact the core taxonomy module in unexpected ways). It should be called "taxonomy" to match what the module is actually called. There are other places where the term taxonomy is explained.

When I posted these comments on the forums, VeryMisunderstood explained the historical reasons why "Categories" got used instead of taxonomy. I certainly understand their point about the term taxonomy, and agree that it's a technical term that many will not know. However, I do not think this is the place to explain what the term means. I think this list should be an exhaustive and accurate list of the modules included with Drupal. Given that most of the other entries correspond exactly to the module and directory names under modules, I think this should follow that precedent. I'll note that the Terminology page, under Taxonomy, does explain the history of using "Category" for "Taxonomy". It also notes that the front-end change in terminology has raised a new set of problems. As a compromise here, we could list the module as "Taxonomy" but add a non-link cross-reference under Categories to clarify.

My suggestion for changes to the Core Modules page are as follows:

Add:

Color: a color picker used by some themes
Taxonomy: a way to organize content

Change:

Categories -- See Taxonomy
Node: base level content management

Delete from this list:

Page: post static pages
Story: post static pages

Take the content for Page and Story and move them to a prominent place on the Node description page. It would also be useful to expound clearly that "Page" and "Story" are special node types (akin to the concept of the #1 user being the super user). Something like:

Insert new second paragraph on Node: The Content [This page would be renamed "Node: base level content management"]

Two special types of node are Page and Story nodes. These two node types are the most basic type of content available on a Drupal site, allowing an administrator to create static pages for their sites. More information on Page nodes can be found at {link}. More information about Story nodes can be found at {link}.

My point is that the Core Modules page should be a clear map of the modules in the base system to anyone who is seeking to use Drupal. This should list unambiguously what they should expect to see in the Modules folder, so that they can be sure that they have all the right files in the right configuration. As it is, people have to make assumptions about what is on their own server versus what is listed here.