1. Drupal at ASU
Jeff Beeman
jeff.beeman@asu.edu
@asudrupal | @doogiemac

2. Who we are

3. Web consulting services

4. What we do

5. Shared Web Hosting

6. Contracted dev

7. Core services

8. Core services

9. Drupal + ASU Webauth

10. ASU (Zen) theme

11. Enterprise Drupal

12. Enterprise Drupal

13. Support & consulting

14. Community

15. How’d we get here?

16. asu.edu in 2006
• Over 1 million pages; ~500,000 hits per day
• Fractured online services; Decentralized IT
• Little collaboration and cooperation
• 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

17. 2006: Balkanization

18. 2010: Drupalized

19. Biggest obstacle: Politics

20. Politics
• Territorial site ownership
• No incentive to unify
• No supported tools
• No community

21. The approach
The velvet glove
a.k.a.
Carrot vs. stick
Make Drupal so tasty people
can’t resist moving to it.

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

23. Tactic #2:
Community
• Web Community
• ASU Drupal Users Group
• Drupal Office Hours
• Training: Lullabot / ASU
• Support & Outreach

24. Today

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

26. Hosting environments
• Shared hosting
• High-performance
• Enterprise
• Cloud

27. Future

28. Challenges
• Clean up the mess we’ve made
• Address growing pains
• Cloud / hosted services
• Tools dedicated to Drupal hosting (i.e.
Aegir)
• Data: Usage statistics

29. Challenges
• Change is slow and difficult
• Institutional perception
• Prove Drupal as legitimate
• Focus support efforts
• Training
• Mobile

30. Positive outlook
• Despite the challenges, we’re in a great
position.