Rework Taxonomy help

I took a stab at this for you Xano. I'm sorry it's longer than the original. Be merciless. I can take it.

I also see other issues around the same topic.

I know it's a combination of real stuff, fantasy, science fiction... but this is my best vision of where it can be by september 1.

===

The taxonomy module allows you to manage lists of terms and to describe relationships between terms in the same list or vocabulary. Taxonomy module's vocabularies and terms can have a fundamental role in your site's navigation and your users' success in finding the content they want.

Free-tagging vocabularies are built by users when they submit posts (as commonly found in blogs and social bookmarking applications). The terms in a large free-tagging vocabulary typically do not have relationships to other terms in the same vocabulary because they are created in the context of a site's content by different users.

Synonyms are very useful for free-tagging vocabularies as a way to combine a tag with its common mispellings or variations. For example, your site's content may not need to distinguish a bee from a bumblebee or a hornet. Adding hornet and bumblebee as synonyms for bee allows your users to tag content with bumblebee and for that content to be found with the tag bee.

Controlled vocabularies are complete collectons of terms or names for things. These vocabularies can be very simple with very few terms which are all specific to your site's content. They can also be incredibly complex with mulitple relationships among terms. Controlled vocabularies are most often used to classify a site's content and enhance navigation among related pieces of content.

For a simple example of a controlled vocabulary, consider a recipe site. You might want to classify posts (recipes) by both the type of meal and preparation time. A vocabulary for both of these variables allows you to classify content using each criteria.

Type of Meal: Appetizer, Main Course, Salad, Dessert
Preparation Time: 0-30mins, 30-60mins, 1-2 hrs, 2hrs+

Your content can be classified using multiple vocabularies at the same time and not all content types need to be classifiable by each vocabulary you create.

Each term (sometimes called a 'category' or 'tag') can be accessed at a URL path for HTML and RSS, and simple queries can be performed on a site's content using terms as criteria. [this needs more explanation, a link or be dropped from help. now it's just teasing them.]

In our recipe site example, it then becomes easy to create pages displaying 'Main courses', '30 minute recipes', or '30 minute main courses and appetizers' by using terms on their own or in combination with others.

By default, taxonomy module supports parent/child relationships between terms. You can attach term fields to your vocabulary's term definition [What is that? It's the vocabulary equivalent of the CCK UI for node types that doesn't exist yet.], and these fields are relationships to other terms in that vocabulary or even relationshps between terms in different vocabularies. If you need a "see also" or "superceded by" relationship, use a term field.

In the strictest vocabulary, child terms are similar to their parent term in the same way that their siblings are similar to the same parent term. This is taxonomy module's namesake: the taxonomy of living organisms that shows the relative differences of mammals from reptiles and of reptiles from other reptiles.

However, taxonomy module can be used to create vocabularies that are not strict, hybrid and individualistic. The best web site vocabularies are those that help your audience of users find content using terms from their own human vocabulary.

There are a significant number of contributed modules which you to alter and extend the behavior of the core module for both display and organization of terms. For more information, see the online handbook entry for Taxonomy module.

whatdoesitwant:

Thanks for your help on this issue.

Already, we can cut:

Each term (sometimes called a 'category' or 'tag') can be accessed at a URL path for HTML and RSS, and simple queries can be performed on a site's content using terms as criteria. [this needs more explanation, a link or be dropped from help. now it's just teasing them.]

This is being removed from core because it was badly supported and documented. #503456: Remove multiple tid and depth handling for core taxonomy paths