1 / 37

Sink or swim: diving into Drupal at the ANU College of Law

Sink or swim: diving into Drupal at the ANU College of Law. Fiona McCaskill Drupal South 2014 Wellington. I’m a dog and horse nut. And live in the country. Then. Then. Previously…. Content in home-built cms Internal authentication system for login File access to web server

kaoru
Download Presentation

Sink or swim: diving into Drupal at the ANU College of Law

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sink or swim: diving into Drupal at the ANU College of Law Fiona McCaskill Drupal South 2014 Wellington

  2. I’m a dog and horse nut • And live in the country

  3. Then

  4. Then

  5. Previously… • Content in home-built cms • Internal authentication system for login • File access to web server • Costs: Dreamweaver licences

  6. Previously… login workstation login Finance web directory Web server finance web editor 1 Finance website account login workstation finance web editor 2

  7. Previously…Users • No proper ownership of content • Rogue/orphan sites & pages • No revisions of pages • No logging of editing by users

  8. Previously…Content • Site used as file repository • Content structure reflects internal college structure • Who was the audience??

  9. Why change? • University adopting new branding • Old expensive web server • Half of campus on Drupal

  10. Why change? • Website boring • Tired • Need for a CMS to manage content • Out of date

  11. How we changed • First attempt site wide revision • Complete failure

  12. Challenges that we faced • Staff resistance • Technical hurdles • Deadlines not set • Too hard! Too big! Too much!

  13. How we got round ‘em • Hired a scrum master • Stakeholder buy-in • 1 site at a time (chunks) Our scrum master

  14. What worked • Change is a comin’ • Info sessions • Someone to input content • Meeting with academic directors for each program

  15. What worked • “Hero” site as a demo • “Rules” set by a governing body Styles = branding + w3c accessibility • Training

  16. Our “hero” site

  17. What worked • Prototypes • Client can see functionality available • Less open questions

  18. Our people……then

  19. Our people………now

  20. Old menu New menu

  21. Staff & Student services

  22. Old news

  23. Old events

  24. New news & events! • No coding needed!! • http://law.anu.edu.au/news • http://law.anu.edu.au/events • All achievable without coding just some basic html

  25. Old conferences Image of old conference site • Demo of new conferences site

  26. Old conferences

  27. New Conference site • Consistency • Automated from start to finish • https://law.anu.edu.au/conferences

  28. What worked…. Drupal! • Standard Drupal modules available free • views, panels • Content types, fields…

  29. Views

  30. Panels content (edit mode)

  31. Panels content (view mode)

  32. Content types & fields

  33. Content types & fields field_person_date

  34. How we’re doin… 3 yrs later • 99.99% site chunks of information are live on the new website • Future direction for website set!

  35. Lessons Learnt • Know your audience • Expect staff resistance • Use prototypes and some contrib modules • Set deadlines

  36. Now

More Related