Migrating University of Tartu websites to Drupal

1,462 views

Published on

Behind the scenes: University of Tartu -
Migrating from proprietary CMS to Drupal 7

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Migrating University of Tartu websites to Drupal

  1. 1. Behind the scenes:University of Tartu Migrating from proprietary CMS to Drupal 7 René Lasseron
  2. 2. 18 emp1 internSince 2000 3 500 emp 17 000 stud Since 1632
  3. 3. Before we started• 80+ multilingual sites• Funky navigation scheme• All on one platform Automatweb CMS• Lack of support for the CMS
  4. 4. After we finished the first phase• New navigation• Fresh graphics• Main site with 4 languages on Drupal 7• 70+ sites still waiting for migration www.ut.ee
  5. 5. Scale and scope• 80+ sites on one Drupal installation • 300 daily content editors - One main site www.ut.ee - One main, central administrator - Other sites for Faculties, Institutes, - 50 editors for main site Colleges, other bodies - 250 for other sites - Takes about year and half to migrate - all of them Each having 4..2 language versions • 28 000 nodes on main site • Integrations with 8 backend systems
  6. 6. Login• Username/password against university’s central LDAP, combined with web service• Estonian ID-card and mobile-ID
  7. 7. User interfaceWorkbench• Workbench• Most features hidden from daily editors• Few content types
  8. 8. User interfaceRe-worked tabs• Add new sub-page• Menu and parent menu element gets created automatically
  9. 9. User interfaceRe-worked tabs• Add new nodes of different content types to the page• Creates automatic relations using node reference
  10. 10. User interfaceRe-worked tabs
  11. 11. User interfaceRe-worked tabs Child Main node, defining the menu node, shown via view and node reference
  12. 12. 330 modules“There’s a module for that”• Domain Access • Media • Views (28)• Internalization • Linkit • Context (5)• Display Suite • Autosave • Panel (mostly front page)• Feeds • Content locking • Features (11)• Webform • Google CSE• CKeditor • Link checker IMCE • Transliteration • Simple ads
  13. 13. Custom modules• Trash• Visually impaired• Content reminder• UT title italics• UTTV.ee media support• User bulk operations
  14. 14. Custom modules• Trash• Visually impaired• Content reminder• UT title italics• UTTV.ee media support• User bulk operations
  15. 15. Custom modules• Trash• Visually impaired• Content reminder• UT title italics• UTTV.ee media support• User bulk operations
  16. 16. Custom modules• Trash • Estonian ID-card and mobile-ID support• Visually impaired• Content reminder We are working on• UT title italics publishing these on drupal.org• UTTV.ee Media support• User bulk operations
  17. 17. Visitor’s interface• Omega theme - http://drupal.org/project/omega• 960.gs grid• Nice Primary region feature• HTML5/CSS3• Mobile adaptive• One template for all sub-sites, modified CSS
  18. 18. What we struggled with• Generally trying to create “structure” in Drupal • Menu structure based user access• Showing right stuff on breadcrumbs - - Failed with Workbech Access Waiting for first release of Access• Showing right stuff on • Domain Access needs gentle handling menus - Menu position http://drupal.org/project/ menu_position • Does it all play nice with 80+ sites? • Bugs, patches and patching of modules • Migration!
  19. 19. Deployment and performance• Development, test and live sites • Boost module • Yslow and Google Page• Kept in sync with Features, Git speed recommendations• One live server
  20. 20. Who did it and what’s next• Professional customer • Tools such as Git, Asana, Jira, Liquid planner,• Mekaia: 1 Project manager, 2 backend Harvest, Google Docs programmers, 1 front- end coder • Pushing the limits with• Graphics design:Velvet 70 additional sites• IA: Kristjan Jansen • SEO enhancements • Contributing to drupal.org
  21. 21. http://mekaia.comRené Lasseron rene@mekaia.com

×