1. asu.edu Web in 2006
• Over 1 million pages; ~500,000 hits per day
• Fractured online services
• Little collaboration and cooperation between divisions and colleges
• All kinds of CMSs (or lack of CMS) and languages
• Lack of single university-wide vision for user experience
• No uniform brand
• No universal navigation

2. 2006 Balkinization: No one can find anything.

3. 2009 asu.edu: Drupalized

4. Biggest obstacle:
Politics
• Territorial site ownership
• No incentive to unify
• No supported tools
• No community

5. Approach:
The velvet glove
Make using Drupal so tasty
people can’t resist moving to it.

6. Tactic #1:
Tools
• Standard platform (Drupal + modules)
• Standard environment (shared hosting)
• Standard branding (theme)

7. Tactic #2:
Community
• Web Community
• ASU Drupal Users Group
• Drupal Office Hours
• Lullabot / ASU training
• Outreach

8. Today
• Buy-in from key players • Enterprise environment
• Web hosting environment: • Consistent look; global templates;
20 servers w/ 100 sites each Drupal sites use central theme
• Core sites in Drupal: libraries, • Consistency in apps (modules)
news, student services, etc. • Improved repurposing of content

9. Future
• Address growing pains
• Cloud / hosted services
• Upgrades
• Global includes/theme
• Focus support
• Training, training, training
• Expand community out of ASU