Drupal at ASU - Drupalcon 2010

1,271 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,271
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Drupal at ASU - Drupalcon 2010

  1. 1. Drupal at ASU Jeff Beeman jeff.beeman@asu.edu @asudrupal | @doogiemac
  2. 2. Who we are
  3. 3. Web consulting services
  4. 4. What we do
  5. 5. Shared Web Hosting
  6. 6. Contracted dev
  7. 7. Core services
  8. 8. Core services
  9. 9. Drupal + ASU Webauth
  10. 10. ASU (Zen) theme
  11. 11. Enterprise Drupal
  12. 12. Enterprise Drupal
  13. 13. Support & consulting
  14. 14. Community
  15. 15. How’d we get here?
  16. 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. 17. 2006: Balkanization
  18. 18. 2010: Drupalized
  19. 19. Biggest obstacle: Politics
  20. 20. Politics • Territorial site ownership • No incentive to unify • No supported tools • No community
  21. 21. The approach The velvet glove a.k.a. Carrot vs. stick Make Drupal so tasty people can’t resist moving to it.
  22. 22. Tactic #1: Tools • Standard platform (Drupal + modules) • Standard environment (shared hosting) • Standard branding (theme)
  23. 23. Tactic #2: Community • Web Community • ASU Drupal Users Group • Drupal Office Hours • Training: Lullabot / ASU • Support & Outreach
  24. 24. Today
  25. 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. 26. Hosting environments • Shared hosting • High-performance • Enterprise • Cloud
  27. 27. Future
  28. 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. 29. Challenges • Change is slow and difficult • Institutional perception • Prove Drupal as legitimate • Focus support efforts • Training • Mobile
  30. 30. Positive outlook • Despite the challenges, we’re in a great position.

×