Behind the scenesUniversity of Tartu   Migrating from proprietary CMS to Drupal 7                 René Lasseron           ...
18 emp1 intern     TallinnSince 2000                       3 500 emp                       17 000 stud   Tartu            ...
1996       2001              2009
When we started• 80+ proprietary CMSin  one      multilingual sites• Funky navigation  scheme• Fading technology and  supp...
After 6 months• New live site on  Drupal 7• Mainlanguages site  in 4        university• Fresh graphics and  navigation• 70...
After 12 months• 6 additional sites  migrated• Less bugs• 60+migration waiting  for       sites still
Scale and scope• 80+ sites in one  Drupal installation                                               • 300 daily content e...
Login•   Username/password against    university’s central LDAP,    combined with web service•   Estonian ID-card and    m...
User interfaceFew tools and content types• Most daily editors  from       features hidden• Few content types• Workbench
Re-worked tabsAdd new sub-page-   Menu and parent menu element gets created automatically
Re-worked tabsAdd different content to the page, even different regions-   Creates automatic relations using node reference
Re-worked tabs
Re-worked tabs                                          Child            Main node, defining the menu   node,              ...
There’s a module for that350 modules used Multisite and                 Content editing            Views and internalizati...
There’s a module for that350 modules used Multisite and                 Content editing            Views and internalizati...
There’s a module for that350 modules used Multisite and                 Content editing            Views and internalizati...
There’s a module for that350 modules used Integration                   Other -   Feeds with many patches   -   Features (...
Custom modulesTrash
Custom modulesVisually impaired
Custom modulesContent reminder
Custom modulesOthers• Estonian ID-card and  mobile-ID support• Italic titles          Work in progress on                 ...
Public interface• Omega base theme  -   http://drupal.org/project/omega• HTML5/CSS3• 960.gs 12 col grid• Nice “primary reg...
What we struggled withHierarchy and Access control• Trying to create mental  hierarchy in Drupal                          ...
What we struggled withFile management• Need fortens ofplace to  manage            one                  thousands          ...
What we struggled withDrupal UI with long and deep menus
What we struggled withMigrationPreserve all-   Content-   Hierarchy and menus-   Files-   Users-   User’s relation to cont...
What we struggled withMigrationAutomatweb-   Highly hierarchical-   Hundreds of content/object types-   Content often comb...
Deployment and performance• Development, test and  live sites                          • Boost module                     ...
Who did it and what’s next• Professional customer     • Tools such planner,Asana,                              Jira, Liqui...
Niine 11 Tallinn                10414 Estonia                http://mekaia.comRené Lasseron   rene@mekaia.com
Drupal case study: Behind the scenes of website of University of Tartu
Upcoming SlideShare
Loading in …5
×

Drupal case study: Behind the scenes of website of University of Tartu

10,247 views

Published on

Story about migrating public website of one of the oldest universities in Europe from proprietary CMS to Drupal 7. Presented by Mekaia (http://mekaia.com) at DrupalCamp Baltics 2012 (http://www.drupalcamp.lv/).

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

No Downloads
Views
Total views
10,247
On SlideShare
0
From Embeds
0
Number of Embeds
80
Actions
Shares
0
Downloads
16
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Drupal case study: Behind the scenes of website of University of Tartu

  1. 1. Behind the scenesUniversity of Tartu Migrating from proprietary CMS to Drupal 7 René Lasseron DrupalCamp Baltics 2012
  2. 2. 18 emp1 intern TallinnSince 2000 3 500 emp 17 000 stud Tartu Since 1632
  3. 3. 1996 2001 2009
  4. 4. When we started• 80+ proprietary CMSin one multilingual sites• Funky navigation scheme• Fading technology and support
  5. 5. After 6 months• New live site on Drupal 7• Mainlanguages site in 4 university• Fresh graphics and navigation• 70+migration waiting for sites still www.ut.ee
  6. 6. After 12 months• 6 additional sites migrated• Less bugs• 60+migration waiting for sites still
  7. 7. Scale and scope• 80+ sites in one Drupal installation • 300 daily content editors - 50 editors for main site - Each in 4..2 languages - 250 for other sites - One main site www.ut.ee - One central administrator - Other sites for Faculties, Institutes, - Colleges, other bodies Takes about two years to migrate • Volume them all after completing fist stage - 28 000 nodes on main site - 925 menu items - 20 000 document files in public folder • Integrationssystems 8 backend with
  8. 8. Login• Username/password against university’s central LDAP, combined with web service• Estonian ID-card and mobile-ID
  9. 9. User interfaceFew tools and content types• Most daily editors from features hidden• Few content types• Workbench
  10. 10. Re-worked tabsAdd new sub-page- Menu and parent menu element gets created automatically
  11. 11. Re-worked tabsAdd different content to the page, even different regions- Creates automatic relations using node reference
  12. 12. Re-worked tabs
  13. 13. Re-worked tabs Child Main node, defining the menu node, shown via view and node reference
  14. 14. There’s a module for that350 modules used Multisite and Content editing Views and internalization and organizing layout - Domain Access (vs - CKeditor with custom - Webform with multisite) styles Clientside validation - Internalization - IMCE vs Media - Simple ads - Custom module for - Linkit - Views (31) allowing same alias in different sites - Diff and revisions - Display Suite - Transliteration - Autosave - Context (7) - Content lock - Panel (few) - Link checker - Menu firstchild - Automated logout
  15. 15. There’s a module for that350 modules used Multisite and Content editing Views and internalization and organizing layout - Domain Access (vs - CKeditor with custom - Webform with multisite) styles Clientside validation - Internalization - IMCE vs Media - Simple ads - Custom module for - Linkit - Views (31) allowing same alias in different sites - Diff and revisions - Display Suite - Transliteration - Autosave - Context (7) - Content lock - Panel (few) - Link checker - Menu firstchild - Automated logout
  16. 16. There’s a module for that350 modules used Multisite and Content editing Views and internalization and organizing layout - Domain Access (vs - CKeditor with custom - Webform with multisite) styles Clientside validation - Internalization - IMCE vs Media - Simple ads - Custom module for - Linkit - Views (31) allowing same alias in different sites - Diff and revisions - Display Suite - Transliteration - Autosave - Context (7) - Content lock - Panel (few) - Link checker - Menu firstchild - Automated logout
  17. 17. There’s a module for that350 modules used Integration Other - Feeds with many patches - Features (13) - LDAP - Google CSE
  18. 18. Custom modulesTrash
  19. 19. Custom modulesVisually impaired
  20. 20. Custom modulesContent reminder
  21. 21. Custom modulesOthers• Estonian ID-card and mobile-ID support• Italic titles Work in progress on publishing these on• User bulk operations drupal.org• Media support for www.uttv.ee
  22. 22. Public interface• Omega base theme - http://drupal.org/project/omega• HTML5/CSS3• 960.gs 12 col grid• Nice “primary region” feature• Mobile adaptive• One theme for sub-sites sub-themes for main site,
  23. 23. What we struggled withHierarchy and Access control• Trying to create mental hierarchy in Drupal • Menuaccess based user structure - It’s everywhere around us - Main site: 50 editors, 28 000 nodes, 4 languages• Persisting menusViews drilling down on when - - Failed with Workbench Access Waited for first release of Access Control Kit - Menu position http://drupal.org/project/ menu_position
  24. 24. What we struggled withFile management• Need fortens ofplace to manage one thousands • IMCE of files with folder - Existing folder hierarchy hierarchy and access - Existing access control control - No paging• Media vs elFinder vs IMCE
  25. 25. What we struggled withDrupal UI with long and deep menus
  26. 26. What we struggled withMigrationPreserve all- Content- Hierarchy and menus- Files- Users- User’s relation to content- Content ID’s- Aliases
  27. 27. What we struggled withMigrationAutomatweb- Highly hierarchical- Hundreds of content/object types- Content often combined #something# includes. Example: !!!!!!!!!!!!!!!! Hello,visitor #welcome(text# Pleasedownload#file(1#orsee #link(3#orsendussomefeedback: #feedback(form# #contacts(table# !!!!!!!!!!!!!!!!
  28. 28. Deployment and performance• Development, test and live sites • Boost module • HTML and Google Page and Apache level• Kept in sync using Features, Git Yslow speed recommendations• Separateservers and MySQL HTTP
  29. 29. Who did it and what’s next• Professional customer • Tools such planner,Asana, Jira, Liquid as Git,• Mekaia: 12Project manager, backend Harvest, Google Docs, Skype programmers, 1 front- end coder. 7 persons during one year. • Pushing the limits with• Graphics design: Velvet 60 additional sites• IA: Kristjan Jansen • Contributing to drupal.org
  30. 30. Niine 11 Tallinn 10414 Estonia http://mekaia.comRené Lasseron rene@mekaia.com

×