Proposed Sessions

Drupal 8 will be all about the new: A solid new feature set; a new underlying architecture; a new collaboration with the rest of the PHP world; a new release cycle; an emphasis on new web technologies; and above all, new opportunities for content strategists, site builders, developers, and the co

Migration code written over the life of a project often grows beyond its originally expected size and complexity. This dynamic makes regression testing a useful addition to custom code extending Migrate module.

Are you familiar with PHP and looking to start using the newest version of Drupal? Have you built modules for earlier versions of Drupal and would like to know how to update them? If you answered "yes" to either of these questions, then this session will help you out!

It is an unfortunate reality that Content Creators are often the last group considered when setting priorities for a site build. There are a number of reasons for this, such as politically-weighted stakeholder selection or fixed project budgets.

A general approach to debugging Drupal problems will be presented, followed by an overview of a variety of tools such as the Devel suite, krumo, xdebug, study, and client side debugging such as Firebug and chrome development tools.

Over the past year, we've pushed the limits of Drupal creating the Demo Framework. Intended to be a starter kit for promoting enterprise-ready Drupal solutions, we use this framework to demo Drupal to our potential clients.

For the last several years the Drupal community has had a conversation about the best way to set up version control on a Drupal site that has a proper development stack consisting of local, development, staging, and production environments.

Today lots of different companies and organizations are trying to be Agile in their web development practices and projects... and many of these are using Drupal either to build solutions for themselves or for others.

The Themers of Drupal have for years been whining & moaning over the bad markup, confusing theme functionality, Drupals lack of separation from the frontend to the backend and generally WTF when you work in the frontend.

Or no. Or maybe--I guess it depends. Although Drupal is typically considered a CMS, it provides a great deal of functionality that is useful beyond just working with nodes. At it’s core Drupal provides a powerful yet flexible framework that can be utilized to build an app.

Need to very quickly set up a payment form that accepts credit card online? But in a way that is professional looking, reliable, safe, secure, and PCI-compliant? And integrated with your existing Drupal website using the Webform module?