Developer tools

Features Scripts are command line shell scripts designed to help with building Drupal sites using Features, Drush and Drush Make. It actually automates the processes of installing new Drupal sites and adding new features to them, both used in site building.

Overview of the concept

These scripts assume the following:

• Your site is been build fully with the help of features. Therefore there is a need to separated everything what is related to a particular functionality into a particular feature module.
• A feature is bundling not only it's exportable components, but also a make file for downloading its dependencies, and a shell script for making all the other changes related to a feature where needed.
• Your starting point, all the functionality which you need for using this workflow (all what is on top of a naked Drupal install in this case) is bundled in a feature which we call the basic feature. The script contains only how to download and install Drupal and this basic feature.

Usage

Scripts are designed to be executed from the root path of a Drupal site or independent
of any Drupal sites entirely.

Examples

This module provides integration for the SlideDeck™ jQuery plugin with Views 2.

Themepacket module helps Themers and Developers create and override theme implementations quickly and naturally by eliminating the need to manually register theme hooks in your modules and themes. This module will also discover any assets found with your theme implementations (css, js) and drupal_add_* on your behalf.

Context Keywords provides a context condition reactive to the searched keywords used to find your site. This opens up the possibility of customizing a user's experience according to keyword patterns the context administrator defines. A default token is also included, which allows activation of a context if no other keyword contexts are active.

This module currently works with Google(incl. Instant Search), Bing, Yahoo and Ask.

This module is currently obsolete as keywords are no longer provided by many major search engines. I'm open to ideas if anyone knows of a workaround.

This module is designed to provide an API for working with a Capsule CRM (http://capsulecrm.com/) account. This module is intended to only provide a programmatic API and an administrative interface for setting account information used by the API functions.

This project is not authorized or supported by CapsuleCRM. For information on the CapsuleCRM please see http://capsulecrm.com.

Included API:

• case (kase) functions:
  • capsule_get_case
  • capsule_list_cases
  • capsule_list_cases_since
  • capsule_list_cases_with_tag
  • capsule_delete_case
  • capsule_add_case_history
  • capsule_add_case_task
• opportunity functions:
  • capsule_get_opportunity
  • capsule_list_opportunity_tags
  • capsule_add_opportunity_tag
  • capsule_delete_opportunity_tag
  • capsule_update_opportunity
  • capsule_add_opportunity_task
  • capsule_delete_opportunity
  • capsule_list_opportunity_parties
  • capsule_add_opportunity_party
  • capsule_delete_opportunity_party
  • capsule_list_opportunity_customfields

When developing Drupal sites, we are often switching between development versions and a production site. Since they normally look identical, it is easy to get confused as to which host we are on.