Room name24. aug 9:00

Drupal Distributions: The Dos and Don’ts

Irakli Nadareishvili, Jeff Miccolis

Tuesday, August 24, 2010

irakli nadareishvili

director of product development

phase2 technology

Trivia: was trained to become a hardcore physicist

Tuesday, August 24, 2010

jeff miccolis

lead developer

development seed

Trivia: studied philosophy in undergrad

Tuesday, August 24, 2010

Agenda• What are distributions?

• Typical architecture of a distro

• Community infrastructure

• Running a distro as a product

• Extensive Q&A

Tuesday, August 24, 2010

What’s a Distro?A Drupal distribution is a Drupal installer packaged differently than the default one on drupal.org

Tuesday, August 24, 2010

Distros vs Default• Expand the reach of Drupal

• Tailored to specific needs

Tuesday, August 24, 2010

Inside a Distro:• Drupal Core

• Installation Profile

• Set of modules

• Themes

• Third-party libraries (e.g. Javascript)

Tuesday, August 24, 2010

Install Profiles• Can only be chosen on install.

• Provides custom install tasks.

• Provides modules and themes that are only available to sites that use the profile.

Tuesday, August 24, 2010

Exportables• Distinguish between content and

configuration.

• Capture the configuration in code.

• Make long term configuration management possible.

Tuesday, August 24, 2010

Toolchain• Features module

• Context module

• Kit specification

• Drush & Drush Make

Tuesday, August 24, 2010

Tip #1Install Profile is just a list of modules!

Tuesday, August 24, 2010

Tip #2• Long list of modules can take a while to

install!

• Use batch processing.

Tuesday, August 24, 2010

Tip #3• Organize Features functionally.

• Separate frequently-changing from permanent.

Tuesday, August 24, 2010

Tip #4• Context Layouts are powerful.

• Always define a global context.

• Beware of overlapping contexts.

• Write a custom condition or reaction if needed!

Tuesday, August 24, 2010

Tip #5• Always fix module versions in your drush

make!

Tuesday, August 24, 2010

Drush Make on d.o.• Benefit: Better automation.

• Challenge: third-party libraries

• Challenge: running custom packaging routines and security

• Current State

Tuesday, August 24, 2010

Localizing a Distro• localize.drupal.org

• Setting up a localization server

• Syncing with l.d.o.

• Translating an install profile and bundling it with .pos

Tuesday, August 24, 2010

Building a Community• OpenAtrium Experience

• OpenPublish Experience

Tuesday, August 24, 2010

Maintaining• Who pays for a distribution?

• Keeping up with security releases

• Packaging

• Upgrade testing

Tuesday, August 24, 2010

Where We’re Headed• The future of distributions?

• Tools we will need?

• Is there a momentum?

• What’s next?

Tuesday, August 24, 2010

http://cph2010.drupal.org/node/5663

Tuesday, August 24, 2010