Under active development

A ctools plugin that renders JSON with mustache (js or php).

Do not use this, this is really experimental right now. It just shows kittens.

A module to provide a views style plugin for bootstrap grids.

Bootstrap is a CSS framework created by the good folks at Twitter, to speed up layout development.

The regular views grid style plugin uses tables which are not ideal in terms of semantic HTML, and not really doing things in a 'bootstrap' way.

This module (via the views plugin) provides grid-based markup in a bootstrap friendly way - wrapping each row of items with a div.row container.

There are options to configure wrapper elements that allow you to control the display of the view. These elements can wrap:

• Individual items. Useful when being used for field based views, or if you don't want to theme your view modes for bootstrap compatibility;
• The entire display. This allows you to set a wrapper element with an overall width for the display. For example <div class="span8">...</div>.

I use this module actively in projects, but tend to use display suite to control the markup for individual items in the display, using the ds classes to apply spanN classes to each item. I would also tend to theme the output of the block or region to control the width of the entire display.

Integration with Mandrill transactional email, a service of MailChimp. Plays well the MailChimp module, which focuses on lists and campaigns.

The Tripal Network module supports inclusion of biological networks in a Tripal site. It provides:

This is a project to integrate Broadbean services (www.broadbean.com/uk/) to any Drupal website. It has been started as a way of integrating their services with a client website. Their system uses a simple "push" system whereby jobs are posted to Broadbean who then "push" an XML post to one of many websites / services / job board websites. My goal is that one of the websites that they post to is a Drupal website.

Goals:

• Create a "job" content type which contains the default variables which they post OR allow the admin to select a pre determined job post content type for integration
• Allow the user to add cck fields and taxonomy vocabularies to this content type for extra flexibility
• Have an admin screen which displays the desired xml post FROM Broadbean to give to their integration team
• Allows the user / admin to select the desired user for posting OR creates the user called "broadbean" with the required permissions for accepting job posts

What's been done so far:

The Render As module adds the ability for elements to be rendered as a specific user and/or role(s), which can be used for the purposes of testing how content will be seen by another user or a user or a particular role without having to change users.