Expert

Session goal: The goal of this session is to create informative visuals to assist in Drupal adoption.

Introduction: There is a presentation renaissance happening, and people are leaving the old tired bullet points behind. But there is a lack of useful visuals for Drupal. If you write documentation for your modules; if you present proposals to potential clients; if you deliver training, you find you need compelling visuals for your ideas.

The speed of light is, unfortunately, still a constant. If your Drupal site has users in San Francisco, New York, London, Tokyo, Delhi, and Australia (and whose doesn't?), you've had no good way to give all of them fast access to your site. No matter where you put your master database server, most people have to cross an ocean to access it. Perhaps you can put read-only slave databases with local web servers in locations around the world, but then the remote users still have a long haul when they want to log in and create content---which is, after all, what your Drupal site is for.

There are multiple ways to scale your Drupal application and business with cloud computing. The first is being able to horizontally scaling your computing power. The second is being able to leverage the scale that you can get with cloud based data services and content delivery networks (CDN). Imagine taking advantage of all of that on a platform that can place your application in front of hundreds of thousands of potential new customers…

Blocks. Panels. Services. Context. Why are these all separate systems?

That's the question many leading Drupal developers began asking at DrupalCon San Francisco, and some even earlier. What if we could merge all of these systems, and make Drupal context-sensitive throughout? Just how far could we go?

This session is for those who are excited by the great power of Apache Solr search for Drupal and want to take things even further. Do you want take complete control over your search interface and offer more than the default features? Have you ever wondered what it takes to add data to your search index? Curious about defining facets, custom sorting, or making cool new widgets for filtering and faceting? Join us for a technical deep dive into the world of Solr search.

Ever came across a Drupal-project, where data was not simply inserted into Drupal forms and printed as HTML-pages? Where you wanted to:

<

ul>

A common scenario in web development is a delay in serving a page, due to
the need of performing several unrelated operations in sequence.
Sequential development is the norm in every major programming language,
and, although parallel processing is possible, implementing it in your
application is often painful and results in complex and debug unfriendly code.
Enters Gearman, a distributed client/server framework, which can be easily
integrated in any programming language, including SQL (through a MySQL User
Defined Function), and makes parallel processing a trivial task. This

Drupal is increasingly the CMS of choice for large projects. The popularity of the platform means that developers and businesses need robust tools to manage their deployments.

Managing a handful of production Drupal sites is pretty straight forward. When you start deploying or trying to manage hundreds or even thousands of sites, things get complicated very quickly. Dave Hall will explain how he has used Aegir and Drupal to deploy and manage thousands of production websites.

(Here is the presentation)
[Update: Several people asked for a writeup on how to run a catchall Apache virtualhost]

There are bugs in every piece of software, and Drupal is no exception, and your site is no exception either. You just have to be prepared to deal with the bugs. Learn effective strategies to approach them, handy techniques to find them, and get your tools set up and mastered.

Drupal 7 has vastly improved dynamic forms capability, and oh-so-much easier for the developer.

This session will enable you to use dynamic AJAX forms (which allow parts of the form to be rebuilt without a page load, giving your visitors an improved experience), and the new #states feature, which allows parts of a form to be shown/hidden/changed based on other parts.

Who is this for? Any developer who wants to build forms using the From API. This will be accessible to anybody who has ever seen the Drupal Form API, and there is no Javascript involved at all.

This will cover: