nodes

This module uses ctools context, content types, access and export to create a small, efficient extension of the Drupal 7 core block system. The project includes some examples that demonstrate the basic functions.

Taxonomy terms appear as an unordered list in the bottom of a node via the $term in the node template file.

However in some cases it could be useful to change this default display. For example, to keep terms separated into their respective vocabularies and label each group with it's vocabulary.

The 'template' plugin for TinyMCE allows a user to select a HTML template from a drop-down and insert it into the WYSIWYG text-area. This module supports that TinyMCE plugin for use with the WYSIWYG API, but of course, if anyone wanted to provide additions for FCK or other editors I'll be happy to include those too.

This module provides two additional Views display plugins, "Profile" and "Node content". These displays do not display on a page but get "attached" to either a user page or nodes of specified types. These views are not stored with the user or node, the way viewreference.module would, so they can be globally-reconfigured.

The node content display can be reordered on the "Manage fields" tab if CCK is enabled. If not, it will have a weight of 10 so it floats to the bottom of the node.
Usage tips

Allows node editing access based on menu relationships.

The Menu Node Edit module allows the site's menu system to be used as the sole organizing principle. It does so by allowing specific menu items to be defined as 'sections' of a Drupal web site. Individual users can then be assigned as editors of one or more sections.

Section editors are then granted access to edit all nodes that fall within a specified menu hierarchy.

This views module creates a relationship that ties the location of a referenced node to the referring node.

Allows you to configure a CCK user reference field so that the user whom is referenced in a node is granted access to view the node. There are also options to give the user access to edit or delete the node.

This is great if you want your node authors to be able to choose additional authors, or choose who can view their node, as well as being able to display the list of authors or viewers in your node, or in Views. If you just need to administer view/edit grants on nodes without the CCK field you should use the Nodeaccess module.

Hides preview button on node editing pages