Features Package

The System Features module provides integration between "system objects" (modules and themes) and Features. It makes it possible to export module status to a feature, which, when deployed, can enable or disable modules, or change the weight of modules.

It is primarily intended for use in scripted deployments, as a convenient way of making changes to the status of several modules at once, via the standard Features mechanisms.

TODO:

• Support for Themes

Part of the Debut features set, Debut Comment provides some of the most commonly needed functionality for handling user comments.

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

Installing

You have two options for installing Debut Comment:

• Debut Comment 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:

• Comment notification using the Comment Notify module.
• CAPTCHAs on comment forms for spam prevention using the Captcha module.
• Login enhancements using Logintoboggan.
• User permissions.

A feature integrating Spaces to distribute content among multiple subsites, each with their own features.

Setting up Spaces to use taxonomy for sub-sites is complex. This module does the setup for you.

Includes:

• Creation and configuration of a Sites vocabulary for assigning content to different sub-sites using the Spaces module.
• Configuration of Persistent URL

Part of the Debut features set.

A tagging feature providing configuration a freetagging vocabulary with automatic tag suggestions based on node body content.

Includes:

• Creation and configuration of a Tags vocabulary for freetagging.
• Automatic tag suggestions using the Tagging and Extractor modules.

Part of the Debut features set.

A feature-based version of Case Tracker, which relies much more heavily on standard Drupal modules like CCK and Comment Driven, and is thus much more extensible. Contains nearly 100% of the functionality of Case Tracker, and then some, with Gantt charts, progress and duration fields, and task dependencies out-of-the-box. Included submodules provide Open Atrium integration and migration from Case Tracker and Storm environments.

About

The WordPress XML for Feeds module exposes WordPress-specific data in WXR files (that's "WordPress eXtended RSS") to the Feeds module. It also includes the WordPress Importer module (a features-package), which imports WXR files using Feeds and the WordPress XML parser.

Please refer to DruStack Core for on going development.

Watch a demo video of this module!

The Ubercart Event Registration module is a feature package paired with a small 'glue' module which yields a simple event registration system. The main goal here was to tie together webform module with Ubercart 2.x to give us a registration sign-up form which could have completely custom and unlimited form information, unique to each event, which can be updated easily by a site editor with limited Drupal experience.

Atrium Leads is a simple Open Atrium feature that provides a "Business Lead" content type.

This can be used for keeping track of the status of any kind of business lead, ie. potential clients, RFPs, job offers, or even for tracking candidates for hire.

It offers a simple content type with fields for Description, Link, Contact Information, Keywords, and Status (New, Contacted, In progress, Closed, Abandoned).

It also provides views for navigating through leads by status and tag. Everything is based in Views and CCK so further customization is possible.

The main idea - to provide universal interface using feeds module for doubleway syncing
- content type fields (cck (d6), field api (d7)) with object fields from openerp
- openerp object fields with fields from drupal content type (mostly usefull for Product(drupal) <-> product.product model(openerp))