Site structure

Read the contents of a post (aka node) and attaches appropriate taxonomy tags. It uses the Yahoo Term Extractor service to find these tags.

Includes

The CiviCRM Group gmap module allows you to create pages that display Google maps of your CiviCRM groups. It requires the Gmap module and the CiviCRM module.

Allows a user to use a taxonomy hierarchy to pre-select a list to be used as a select list (e.g. drop down)

The Taxonomy Search Widget is an addon widget to the node reference field type. It allows the admin to set up a taxononmy vocabulary that the user can select from to limit the node selection to only those nodes tags with a specific taxonomy term. It uses AJAX to update the selection widget.

Say you have pages on animals tagged with a taxonomy, and you have a content type that node references one of your animal pages. This widget means that the user first selects the type of animal, giving them a manageable selection box to find the right animal page from.

In short - all this does is make it nicer for the person selecting the node reference....

No extra data is stored in the node.

let take that step by step. Lets assume you have 100's of products, each of which is a node. Now, lets say you set up a vocabulary called productType. Each product node is tagged with one of the terms from your vocabulary (taxonomy).

Implements a Views plugin to display tagcloud-like list of everything handled by views, using the tagadelic module.

Assign permissions to vocabularies by user role.

The core taxonomy system allows vocabularies to be assigned to node types. This module extends that by allowing the editing and/or display of the vocabulary to be controlled by user role. It attaches itself to the vocabulary add/edit form and gives the administrator three options for each role - (1) edit and view, (2) view only, and (3) none.

This module makes it possible to create a vocabulary for administrator purposes, hide this category from most users, and then use the category as a views filter.

Here are two use cases:

• a vocabulary that had the terms "special offers", "front page", "user advertisement", etc; this vocabulary could be used in various views to pull the tagged content into a particular block or page.
• a vocabulary that had the terms "editor post", "editor tagged", and "community post" and a role type of "editor" that was less than an admin, but had privilige to write editorial content (as opposed to unedited community content), but also had permission to tag community content as something that was propogated to higher visibility.

A simple module which allows you to create menus from image files. Supports title (displayed when hovering over a menu item), alt text, weights and optional mouseover behaviour.