Document how docs team uses the issue

Sheldon, I agree submitting issues could be easier. It's an important goal for Drupal.org to make this easier. Here's what I suggest you do.

1) Check and see if there is an existing issue addressing this.
2) Post this issue in: http://groups.drupal.org/designers-and-information-architects
3) When a designer gives a mock-up of how it can be improved, the project module maintainers can review it.

Cheers,
Kieran

We would like to include the way that docs uses the issue queue in the new reorg for contributing. Please feel free to help out with sketching out some explanations to be included in the new Documentation section (http://drupal.org/node/240242). Unfortunately docs don't line up well with software tracking. Also reagrding the components not matching up right now (they should match the different books pretty much), we have changed handbook sections around quite a lot and there is an issue to update the components to match (http://drupal.org/node/236767.)

The docs in CVS means exactly that - documentation that is stored and maintained in CVS rather than the handbook, not documentation about CVS. That would be under developer docs currently, but will be moved to the new contributing section once it is created.

I'm going to change this to a docs issue re: documentation.

Part of the problem is that renaming component values is risky (see #140989: Renaming components is unsafe) in a sense. So, over time, what once might have made sense as a component no longer is as relevant or as descriptive as it once was, yet changing the name of the component may not be a viable option.

The various books have been renamed as well. The current names predate a lot of things. I have some thoughts for later when things settle down but the transition will be gradual

In the last week, the documentation team has re-done the components, so helpfully this is much clearer.
Please see more about the new component categorization. See http://drupal.org/node/301443