Simple ways to bridge gap between related nodes through CCK

Issue Summary

Hi this is this an idea. I have read from documentation more than I have contributed, so I am trying to bridge the gap and come up with sensible ideas. These ideas aren't difficult or even new, I was just looking for content and wanted to see some action done when it comes to finding the documentation I (and perhaps others) need fastest/most.

I have 2 ideas when it comes to making more sense out of navigating our huge documentation thing.

Tagging for nodes

A well-executed, high quality tag system.

I feel that tags may be intimidating because when not customized or regulated, they may not be useful. I think tags should be high quality identifiers which would relate nodes that otherwise could be 2+ degrees of separation away (quite possible with a hierarchical structure).

Tags should be add conservatively. Not in a competition to get "node visitors" (heh, so doubtful). People should be able to delete junk tags that aren't part of the big picture.

We would develop an algorithm to show related content through tags.

Hand-picked nodes (Autocomplete node CCK field_

Quick links and Related content
Quick links can be a fast way to drill down to a particular section of a handbook hierarchy.

Related content can be similar stuff in different handbooks/sections.