"The Universe" room

Overview

This session will focus on taking full control of node displays. It will be geared toward intermediate and beginner Drupal themers.

Agenda

* Using Devel module to build node templates
* Templating with Zen theme
* Creating clean and maintainable templates
* Adding and changing node variables
* Working with CCK and node templates
* Panels 2 for node displays
* Using custom node templates for views
* Customizing node component displays such as taxonomy and links

Goals

Attendees should leave the session feeling confident that they can template the most complex displays.

Requirements

Fluency in xhtml and a (minimum) beginner's level of php will be needed.

Overview
We propose to show you the making-of boucheron.com, an e-commerce Drupal website we've built for two years, with a full Flash front-end. We'll also present some bits of the specific backoffice and how in/out dataflow works.

Agenda

* Flash and drupal, how to make them talk together
* Used modules for ec-commerce
* Creation and extension of e-commerce modules
* Creation of the backoffice
* Integration with others informations system : ERP, CRM, AS400

Goals

Understanding the building parts by parts of a successful e-commerce service in an international context using flash for a luxury user experience.

Resources
* ecommerce website
* company data flows

Overview

The Drupal association is non-profit organization that provides support for the Drupal community via events such as Drupalcon, marketing of Drupal, and support for Drupal.org.

Agenda

* Update on Drupal.org improvements
* Discussion about Drupalcon North America 2008
* Legal update from Bert and Larry
* Marketing from Kieran
* Drupal association permanent members elections Jan 2009

Goals

The purpose of this meeting is to share progress in supporting the Drupal community and to learn about emerging issues in the community that need support.

Resources

Bandwidth for remote Drupal association members.

Overview

Drupal is increasingly making a place for itself among museums around the world. As a strong and flexible framework Drupal can be a good fit for these sorts of organizations.

This session will be a case study and lessons learned from two museum web sites Palantir has built using Druapl 5: The Indianapolis Museum of Art and the Art Institute of Chicago. Both sites offered a number of unique challenges but also the opportunity to share amazing and diverse content.

Agenda

* Bringing Drupal into a large, established web presence
* Designing a modern site that still has a strong artistic feel
* Bridging Drupal to legacy multimedia databases, such as museum collection databases
* Drupal as an application framework
* Existing open source museum tools

Goals

We hope to present both the challenges and rewards of integrating Drupal with large, established systems such as those of museums. We also hope to give some insight into how to bend Drupal farther than you ever thought possible.

Resources

Indianapolis Museum of Art: http://imamuseum.org/
IMA Drupal.org Showcase: http://drupal.org/node/188312
Art Institute of Chicago Collections: http://www.artic.edu/aic/collections/
AIC Drupal.org Showcase: http://drupal.org/node/279485

Overview

User experience (UX) can be defined as “the overall experience and satisfaction a user has when using a product or system.” A product’s UX affects a user’s interest, ability, and enjoyment when using a product. If a product’s UX sucks, people will not use it if they have a choice or hate using it if they do not.

Well, programmers are people, too. When creating a software product like Drupal that is intended to be used by other developers, the UX includes the experience of those developers as they write code for the product.

Since developers face different kinds of issues than the end users of the product, it is useful to consider Development Experience (DX) distinctly from UX. DX might be defined as “the overall experience, satisfaction, and efficiency a software developer has when using a software development platform.”

In this workshop, we'll brainstorm about ways that Drupal's Developer Experience can be improved.

Agenda

* Why Developer Experience matters
* Open discussion of how Drupal's DX can be improved.

Suggestions I'll bring the workshop include using defined names instead of anonymous constants, abandoning anonymous arrays in favor of typed data structures, and replacing form submit handlers with API functions. Please bring your own!

Goals

We'll come up with a list of proposed coding style directions or improvements for Drupal 7+ and contrib modules that will make Drupal a much more enjoyable and efficient platform for which to develop.

Resources

Anyone familiar with Drupal development is qualified and encouraged to attend. In many ways the less experienced you are, the better, as you will not already be indoctrinated into The Drupal Way of doing things.

Overview

This session will show off the results of Drupal's Google Summer of Code 2008 projects. Students who make it to Drupalcon will be demoing their own projects, and we'll also show off projects from the students who can't be there.

Agenda
The following projects will be shown during the course of the session, as time permits.

• Apache Solr Improvements
• New Aggregator for Drupal core
• Bookings API
• Charts module Views integration
• Color module improvements
• Document Import Module
• Embed Widgets
• Revamped Help system
• Icon module
• Image manipulation GUI
• Memetracker
• New nodequeue sub-modules
• OAuth/Services module integration
• Open ID Attribute Exchange
• PluginManager
• Core search improvements
• Security scanner
• Usability Suite
• Validation API
• Version Control API / Project module integration
• Views datasources

Goals

This session will allow Summer of Code students to show off their hard work, and for the Drupal community to get a first-hand look at all the cool stuff that was produced over the summer. Summer of Code students typically make excellent employees as well, for those looking to hire. ;)

---

NOTE TO ORGANIZERS: I put down "90 minutes" because that'd be a much more comfortable time frame during which to show off 21 projects. But every other year we've managed to do it in 60, so if 90 minute slots are short, you can push the time allotment back.