Developer

Note: It has been brought to my attention that this module duplicates existing functionality in a couple of modules: Demo and Drupal Reset. I was unaware this capability was included in Demo, and Drupal Reset sprang up between the time I developed the module for personal use, and when I got around to adding it to contrib. Apologies for the duplicate effort; I will not be continuing development on this module and encourage you to use Demo instead.

The Self Destruct module is a developer utility for quickly emptying/resetting a Drupal site's database.

This module is useful for developers who want to fill the site with a content skeleton.
From a titles list and a standard body content, you can create the corresponding nodes (having choosen the adapted content type). You can set a menu to put the nodes in and a term to tag with.

This is not a content import, neither a complete fake content creator : it's a mix between this to simply create the skeleton of your site with true nodes containing a temporary content.

To come, if needed : add multiple terms, general settings (like authorized content types).

Software Projects is a bundle of configuration that adds issue tracking features to an Open Atrium project. Open Atrium comes with an issue tracking system that is based on the Case Tracker module while OG Software Projects is based on the "Project" modules.

2.x branch

The 2.x branch will be a complete rewrite (by hand, for the most part).

My vision for this module is the glue and extra parts required to create a system like Unfuddle. I will be using Open Atrium, primarily, but I would like to build the module in such a way that it will work on any Drupal site.

Widgets enables you to centrally manage and configure code snippets on your site such as share and follow buttons or Twitter updates and Facebook like boxes. It implements a user interface that allows you to easily organize and configure various widget elements. Using a UI similar to core’s image styles, elements can be assembled into widget sets which can be reused throughout the site via blocks and other render displays.

CD Deploy is a Webserver for Drupal that runs from a CD/DVD media on Microsoft Windows 9x/ME/XP and Vista.

Technology

In order to run a Drupal site you basically need:
- Web Server
- Database Server

CD Deploy does a "pack" of all the stuff needed, copying it into a folder called "app" which you can then burn to a CD/DVD. How does such pack is build? Well, it uses two technologies:
- make
- Nullsoft Scriptable Install System (NSIS)

Provides an API for defining rules for rewriting the menu paths.

For example:

/**
 * Implement hook_menu_rewrite_rule().
 */
function development_menu_menu_rewrite_rule() {
  // Make 'Development' a primary item.
  return array(
    'admin/config/development' => 'admin/development',
  );
}

/**
 * Implement hook_menu_rewrite_alter().
 */
function development_menu_menu_rewrite_alter(&$items) {
  // Ensure 'Modules' menu item shows up first.
  $items['admin/modules']['weight'] = -11;
}

Adds support to Views to filter a block on a node page by that node's taxonomy terms.

Show aliases module enables privileged users to see, edit, and delete all url aliases (paths) assigned to a node, from within the node edit page.

We don't recommend you delete aliases on a site that has seen the light of day, unless you are manually moving extra aliases into a set of redirect definitions (as in a .htaccess or virtual host file) which was the original reason we wrote this module.

DrupalORM provides a programmatic ORM interface to nodes and their corresponding CCK fields.

Assume you have a content type called "page" with the following node and CCK fields...

• Node title
• Node body
• CCK Field "field_desc"
• CCK Node reference "field_ref" which points to content type "story"

You could query "page" content type in the following ways...

Dialog provides an API for opening content in an interactive overlay.

Dialog is a backport of the Drupal 8 Dialog API for JavaScript.

Requirements

Dialog has one dependency.