Actively maintained

Embeddable provide a method for embed thingies in content.

It is a pluggable system that currently allows the embedding of nodes and blocks.

It functions by placing a div in the content with attributes that describe what is to be embedded. ie for nodes the nid and the view mode are attributes. Then after the page is build the div is converted into the embed content.

We hope to add an option to do the transformation in js in the feature.

also look to allow embedding of other entities.

This module provides a field type for referencing terms with a level to an entity, e.g. someone can add the term "Java" with the level "Expert" to a node. The levels can be defined in the field settings and consist of a numeric level key and a human readable level label. The structure of the specified vocabulary either has to be a flat-list or a single hierarchy with two hierarchy-levels, where the parents act as grouping terms.

This module, to be used with the Flag module, wraps flagged items with useful CSS classes. For example, a bookmarked node will be wrapped with a class="node-flagged-bookmarks-self" that can be used to theme the node.

This module is a Phoenix from the flames! New maintainer, new ideas, new challenges. Drupal 7 version on the way...

This module is abandoned in favour of:
http://drupal.org/project/drush_make_ui

The "Remove links from teasers" module is a simple module that
removes the "Add new comment" and "Log in to post comments" links from
teasers.

This module provides an input filter to add a gist (from Github) anywhere input filters are accepted. You have the option of replacing the filter tag with a link to the gist or embedding the gist itself.

From Github:

Gist is a simple way to share snippets and pastes with others. All gists are git repositories, so they are automatically versioned, forkable and usable as a git repository

It is by far the easiest way to embed code in your site, with syntax highlighting and all.

Allows users to locally rearrange and roll up panes on the panel and save the state per account. Global state of the panel is not modified in the process.

Note! 7.x branch is in development and unstable, currently only available as a 6.x module.

Dependencies

• Panels
• jQuery UI

If you're using non standard, custom layout template, please ensure that .panel-display class is present on root div of your panel layout template.

The LT4L module provides a connection between the tagging of Drupal content and the items in a library's catalog. With the LibraryThing for Libraries service, libraries can set up accounts, upload information about their catalog, and tag items within it. When a library patron views an item in the online catalog, LibraryThing for Libraries presents related content via tags.

How does the LT4L module work?

Part of the Debut features set, Debut Wysiwyg provides Wysiwyg module integration including configuration for Wysiwyg editing and accompanying input formats and Media module integration for adding file assets to text areas.

Like all Debut features, Debut Wysiwyg can be integrated either as a stand-alone feature to quickly add Wysiwyg functionality to any Drupal site or as part of a Drupal distribution. Debut Wysiwyg is used in the Open Outreach Drupal distribution aimed at nonprofits.

Installing

You have two options for installing Debut Wysiwyg:

• Debut Wysiwyg is used in the Open Outreach Drupal distribution aimed at nonprofits, so you can install it as part of Open Outreach.
• Install manually along with the dependencies listed below.

Includes:

• Three input formats: Wysiwyg public, Wysiwyg contributor, and Wysiwyg editor.
• A Wysiwyg profile for each of the input formats, including edit buttons designed to meet the common editing needs of users with varying roles.
• Incorporates the Media module for inline insertion of media.
• Uses the Entity module to export the input formats.
• A Drush Make.make file with all dependencies, including the CKEditor.

Drupal core development needs to be chunked in lengthy stable releases. But sometimes, we want core-like stuff on a faster schedule.

The Drupal core development rules are applied. All patches go through regular peer-reviews. No API change once we hit a stable, but of course, this module is able to release new major versions.