Utility

Dear developer:

Inline CSS is the bane of our existence. But clients and marketing types love it and use it all the time. Probably because we aren't giving them the flexibility they need.

Inline CSS builds up over time and creates technical debt and visual inconsistencies in our website designs. These become more and more expensive to even identify, much less fix.

Documentation is hard! Developers are often too close to the implementation details to write effective end-user documentation. End-users aren't likely to go outside the application to write documentation.

Multiple text fields on a page often break up the user experience of editing content to an unacceptable level.

This module attempts to fix this issue by collapsing the text format's tips to not be displayed by default, clicking the question mark will toggle the display of the tips.

Twifago is a simple, light, flexible, and good-looking share button implemented by block. Thanks to Carrot for his code that make this module posible.
You can see a demo here.

To avoid future naming issues due to Openstack project renaming, this module has been superseded by the Openstack Queues module.

Overview

This module allows to set HTTP response headers (both standard and non-standard) on pages by various visibility rule settings. Currently the headers can be set by path, content type and user role.

This project adds a new tab to the Results of a Webform. It provides an Ext JS-based grid to view and directly edit Webform submissions.

As of now, I have only tested this module on Drupal 7.x using Webform 4.x. It might work on Webform 3.x, however.

To use this module, obtain the module directory (webform_extended_table) and contained files and directories (via git) and place in your sites/all/modules directory.

Adds module enabling per machine environment to the env project.

Allows putting tons of fields on bundle.

Just for testing out the maximum number of field a bundle can handle before slow down.

About

Core and contrib tokens already do a great job in providing precious meta information on Drupal entities. However, creating a hierarchical breadcrumb from the root term down (or up) to and especially including the current term with a single token is impossible unless you wanted to create custom code snippets as a workaround.

This module is intended to fill just this gap as handy as possible and thus introduces two additional term related tokens: