• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
 

Migrating University of Tartu websites to Drupal

on

  • 1,295 views

Behind the scenes: University of Tartu -

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

Statistics

Views

Total Views
1,295
Views on SlideShare
1,268
Embed Views
27

Actions

Likes
0
Downloads
2
Comments
0

5 Embeds 27

http://drupalcamp.ee 17
https://si0.twimg.com 6
https://twitter.com 2
http://www.drupalcamp.ee 1
http://www.docshut.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Migrating University of Tartu websites to Drupal Migrating University of Tartu websites to Drupal Presentation Transcript

    • Behind the scenes:University of Tartu Migrating from proprietary CMS to Drupal 7 René Lasseron
    • 18 emp1 internSince 2000 3 500 emp 17 000 stud Since 1632
    • Before we started• 80+ multilingual sites• Funky navigation scheme• All on one platform Automatweb CMS• Lack of support for the CMS
    • 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
    • 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
    • Login• Username/password against university’s central LDAP, combined with web service• Estonian ID-card and mobile-ID
    • User interfaceWorkbench• Workbench• Most features hidden from daily editors• Few content types
    • User interfaceRe-worked tabs• Add new sub-page• Menu and parent menu element gets created automatically
    • User interfaceRe-worked tabs• Add new nodes of different content types to the page• Creates automatic relations using node reference
    • User interfaceRe-worked tabs
    • User interfaceRe-worked tabs Child Main node, defining the menu node, shown via view and node reference
    • 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
    • Custom modules• Trash• Visually impaired• Content reminder• UT title italics• UTTV.ee media support• User bulk operations
    • Custom modules• Trash• Visually impaired• Content reminder• UT title italics• UTTV.ee media support• User bulk operations
    • Custom modules• Trash• Visually impaired• Content reminder• UT title italics• UTTV.ee media support• User bulk operations
    • 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
    • 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
    • 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!
    • 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
    • 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
    • http://mekaia.comRené Lasseron rene@mekaia.com