Under active development

Translatable custom panels panes with body and optional title, stored as variables.

This sandbox will contain a drupal module to interface a Drupal site with the joind.in website.

For what do we need this?

From joind.in's about page:

Joind.in is the replacement for all those paper submission forms that get left on the floor at the end of an event. The site gives details of events past, present and future, the sessions, timetable and speakers at each, and allows all attendees to register and leave feedback - for the sessions and for the event itself.

But we can do all this in Drupal. There's even a Conference Organising Distribution that will do this. For what do we need this?

1. Data in Joind.in is persistent. I've been to Drupal events and found that six months later when I've wanted to remind myself what talks were given, who gave a particular talk, or see the feedback that the site itself has been torn down. On Joind.in, I can see all data for listed events going back to 2008. I can find every talk I've ever seen at a PHP conference at Joind.in.
2. Because Joind.in stores data on many many events, it is possible to track speaker profiles across multiple talks and events, giving attendees a better insight into those presenting at your event, allowing them to make a more informed choice and increasing the profile of your speakers.

Allow a field to be automatically synced with the assets that are embedded in content.

This module aim to be simplest pdf order generation for Drupal Commerce using the mpdf pdf generation library and Views module.

Configuration

This is a for of Entity View Modes to add Features support.
Ticket: http://drupal.org/node/1425620

Only compatible with Workflow 7.x-1.x versions!