Content editing experience

This is a very simple module which provides an input filter that can be enabled for specific input formats. This filter allows an editor with permission for this input format to embed any available block into content by using the blocks module and delta in the following syntax: [block:{module}:{delta}].

For example, if I wanted to embed the Powered By Drupal block into some content, I would use [block:system:0].

DISCLAIMER 1: Care needs to be taken. For example, if you embed something you don't want anonymous people to see (such as devels switch user form), then it will be embedded into the content and displayed with the permission of the person who "rendered" the content. For example, if you empty the cache and then an anonymous visitor views the page - the content will be rendered and filtered as anonymous and then cached like this.

Automated Tabs from node content.

This module will scan a node and split it into tab sections at each <H1> heading element using the heading title as the tab's title (can be set to split at other HTML/XML elements instead). Any text before the first heading element is encountered will be listed under a tab entitled "Intro".

Primary aims are

• To allow "dumb users" (no insult meant) to create tabbed node content without any extra tasks or commands being required - if they can select "Heading1" in the site's WYSIWYG editor or use <H1> in HTML then they can create tabs.
• To automatically split existing nodes into tabs without re-editing.
• Future: Split imbedded XML record sets into tabbed records.

Configuration Options

"Tab seperator element:"

To change the HTML or XML element used as a splitting point and to obtain the tab titles from. {Default = H1 }

"Default Tab title:"

The title to use for the initial tab when the document/node does not start with the defined tab-seperator. {Default = Intro }

"Include seperator:"

Revisionary allows rights to view and revert revisions to be controlled on a per-content type basis. The most common use for this is to provide wiki-like functionality for specific content types mixed in with a larger site, without giving a broad user base rights to view revisions on all content types.

#D7CX This module got into core and will only be available as a back-port version for Drupal 6.

Provides vertical tabs like http://drupal.geek.nz/static/node-form/default/summaries2.html on the node add form.

This module provides the following features:

• Vertical tabifying all node forms.
• Vertical tabifying the content type forms.
• Vertical tabifying the block forms.
• Specialized CSS for Garland, as well as generic CSS for other themes
• Color module support when both Garland and color.module are used
• Vertical tabbed forms and fieldsets are over-ridable by using your site's settings.php and $conf. For more information see #644790-7: Simplify the module and integrate with form_controller to allow customizations.
• When used in combination with Form module allows you to configure vertical tabs on all possible forms.

Note: This module is being merged into the Mediafront Module. The Drupal 7 version of MediaFront will have the Dash media player included in the module download. For Drupal 6 users, there will be an update to this module in soon time that will add the Dash media player within the Mediafront module.

A media player built for Drupal CMS

This module is a helper module for the new Dash Media Player.

The Dash Media Player for Drupal CMS is a revolutionary, first of its kind, free to use media player built specifically to tap into the power of Drupal CMS! Just imagine… a media player whose content is driven by the power and flexibility of Drupal. With this player, you can truly take advantage of the best of two worlds... the incredible user interface of Flash, and the unparalleled content management of Drupal. Using these two systems together, you can quite literally have your very own Media CMS system! As you will soon see, the Dash Media Player is a truly remarkable player geared up for the rise of Web 3.0.

Dash Media Player Features

Provides generic support for transactional operations linked to content entities. An example of transactional operation is an accounting account, where the content entity acts as the account and each transaction is a charge or payment.