This is a list of modules that are known to integrate with features by exporting their own data via features.
Integrating Modules
| Name | Description | Exportables |
|---|---|---|
| Display Suite | The Display suite module is an API which other modules can use to store and manipulate display data for objects (nodes, users, comments etc). Modules implementing this API automatically get an interface for adding build modes, fields and plugins either through code or via the UI. Key features of the API: | Formatters?Custom Fields? |
| Features | The features module enables the capture and management of features in Drupal. A feature is a collection of Drupal entities which taken together satisfy a certain use-case. | Context, Spaces, Boxes, Strongarm, Page Manager, ImageCache, Views. Weak support for: CCK fields, CCK fieldgroups, Content types, Input filters, User roles/permissions, In development: Custom menus and menu links Taxonomy vocabularies |
| Features Extra | It gives the ability to export various content/settings to be features with Features module and CTools Module. | vocabularies; nodequeues (definitions); block settings; custom blocks (boxes) |
| Features Server | Feature Server allows you to create projects, make new releases of Drupal features and themes, and lets users subscribe to updates via the Update status module provided in core. It is simple by design, asking you to fill out version information for releases and upload packages through a filefield. For greater integration with version control systems or for automatic packaging consider using the Project module. | Server for distributing your features. Editors note:I recommend that features are submitted as a normal module on Drupal.org. Then more people will be able to find your feature. There are some features distributed that way. |
| Input Formats | Input formats is an API that allows for the export and import of input formats like an object. This module makes it possible to export and import wysiwyg editor settings into Features. | input formats |
| Panels | The Panels module allows a site administrator to create customized layouts for multiple uses. At its core it is a drag and drop content manager that lets you visually design a layout and place content within that layout. Integration with other systems allows you to create nodes that use this, landing pages that use this, and even override system pages such as taxonomy and the node page so that you can customize the layout of your site with very fine grained permissions. | Through Features module and Ctools module |
| Rules | The rules modules allows site administrators to define conditionally executed actions based on occurring events (known as reactive or ECA rules). It's a replacement with more features for the trigger module in core and the successor of the workflow-ng module. | Rules, Rules sets? |
| Strongarm | Strongarm gives site builders a way to override the default variable values that Drupal core and contributed modules ship with. It is not an end user tool, but a developer and site builder tool which provides an API and a limited UI. | Variables |
| UUID Features | The UUID Features Integration module provides a mechanism for exporting content (nodes, taxonomy, fields) into a features module. What's that you say? You thought features was only for configuration? This module is meant to be used in the cases where certain pieces of content straddle the line between pure content and configuration. | Content: nodes, taxonomy, fields |
| WYSIWYG | Allows to use client-side editors to edit content. It simplifies the installation and integration of the editor of your choice. This module replaces all other editor integration modules. No other Drupal module is required. | Wysiwyg Congiruration (via patch at the moment: http://drupal.org/node/624018) |