Intermediate

Gábor Hojtsy just had a session a year ago introducing http://localize.drupal.org/ and its a fast growing member of the drupal.org site family ever since. It got the new redesigned theme second (after the Drupal Association) and its features and usability is continually expanded and reviewed.

In this session we'd like to take you to backstage showing how localizing Drupal the software works and how you can plug in your modules and themes to be localizable as well. What's supported on drupal.org and how can you localize your own software you built in-house?

The Examples for Developers project aims to provide high-quality teaching examples for developers. Its code is on api.drupal.org and it's a community project. Here's what it is, how you can use it, and how to contribute to it.

This will include the example modules that are available, how to use them, and what's on the roadmap - how you can help.

Acquia's engineering team have been building DrupalGardens at a fast pace for the past year and now that we are heading into open beta we decided it was time to open up and share what has worked well with the community. Chris Brookins (VP Engineering), Linea Rowe (Director Product Management) and Jacob Singh (Principal Engineer) will take you through a 21-day sprint in the life of the Drupal Gardens team.

This session is for:

<

ul>

If you're looking for love, you looking in all the wrong places. If you're looking for a good geeky time, expanding your Drupal knowledge and making drinking buddies (business partners) you are absolutely in the right place.

We'll be doing rotating pairs, speed dating style with some other surprises thrown in.
Expect to:

• Relax
• Make friends
• Learn something

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.

While Drupal can do many great things via the UI alone, it's full power is sometimes only unleashed when you can write custom modules.

This presentation easy ways to begin module development with the hope of giving your next project a kick start. We will highlight some simple ways to integrate with Drupal that are frequently trgets for requests for customization. We will start from some basic hooks, and point out security, localization and internationalization best practices.

We will take you on a magical journey through code and print using Drupal as our vessel of discovery. Ok, maybe not, but we have been busy working with Drupal to decouple our data from where and how it is presented.

The University of Kent has a history of using Dreamweaver as our main publishing platform for web. We used it for publishing news, the online prospectus, events, pretty much everything. This led us to a situation where we found ourselves with 200,000 pages of content, much of which being duplicated and leading our web editor to the verge of breakdown.

Cloud computing offers many advantages for hosting Drupal sites but also presents several unique challenges. This talk will provide an overview of how Acquia has built Acquia Hosting and the Drupal-as-a-Service platform Drupal Gardens. As part of this, we'll discuss specific issues we've encountered while building on Amazon Web Services (AWS) and the solutions we developed to address them. Topics will include:

• Load balancing: Elastic IP vs. Elastic Load Balancing
• Handling user-uploaded files with multiple web nodes

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?