Site structure

Enable users to leverage a drupal system as a front end to twitter.com (and other sources in the future) allowing them to use drupal as a hub for message aggregation, moderation, and dispatching.

FEATURES
============================================
* Operators, users with access to the drupal system, associate twitter accounts with organic groups. All tweets from followers of those accounts will automatically get pulled into the drupal system as nodes.

* Communications moderation
Operators will then add and moderate posts, voteing on them (automatically dispatching at a configureable value), specifying priority levels, associating with other groups (twitter accounts), marking as a duplicate of another post, and dispatching.

* Detailed search / display interface
Operators also have the abilty of searching for nodes by minutes since last recieved, wether or not the node has been dispatched, the current vote level, and wether or not the node has been prioritized.

* SMS Dispatching through twitter
After a operator deems that a node is valid (ie. it has been verified by an alternate source, it has been assigned a SMS message, and it has been associated with a group) he or she can dispatch it. This is essentially posting the sms message of the node as a tweet for each twitter account (group) that is associated with the node.

The main objective of relevance module is to provide a block of related content that can be extensivelly configured, according to the website needs.

Drupal renders its local page tasks as primary and secondary tabs depending on which task you are, while this module builds the complete task tree to display a (hidden) nested menu.

Update: Still no release version, but as I did the missing CSS stuff, I started to overhaul the whole thing. So, before I provide a public alpha, the following points need to be cleared:

• Settings structure & page stubs
• Help & usage guide / documentation (also to keep track of the architecture)
• encapsulate tree building from theming
• style templates hook as in fivestars / quicktabs
• Preview page for style templates as in fivestars / quicktabs
• finish the block presentation + settings
• "nostyle"-style which refers to a normal drupal menu (for usage in a block)
• "default"-style which refers to the themes original local tasks style
• "basic"-style which would be the one that already exists

Well, and after that initial release, there is more to do:

• clean up the jQuery and remove JavaScript dependency for tooltip (should work with css only)
• Provide more styles, a horizontal one (looks like core Tabs, but completely built), for instance.
• Enhance jQuery with animation
• Integrate Color module

A KML parser for the Feeds module.

This module is obsolete

Drupal 6 and 7 users are recommended to use the excellent Menu Block module which does everything this module does and more.

* * *

The advancedmenus module allows site administrators to create an arbitrary number of blocks for any given menu object in the site. The block settings page for each block allows customization of the starting level of that block, as well as customization of the class attribute values used in the markup of the menus.

Features

Block related

Configuration page allows for the creation of an arbitrary number of blocks based on one or separate menus

Setting for starting menu at any level

Setting for showing only top-level menu items

Markup-related

Menus output as properly nested unordered-lists

CSS-related

Useful classes (i.e. classes in addition to '.menu') on ul elements

Unique ids on all li elements

Drupal-friendly '.leaf,' '.expanded,' and '.collapsed' classes on li elements

Drupal-friendly '.first' and '.last' classes on li elements as requred

All 'Drupal-friendly' classes configurable per-block from block configuration pages

Upcoming features

This module provides helper functionality for parsing data into taxonomy terms / pages.