1 / 9

Cross-College Collaboration for Web Services Excellence

Learn about the evolution of web services at the College of Life Sciences and College of Medicine, Dentistry, and Nursing, from pre-March 2012 to present. Discover the principles guiding the merger of web teams and explore the benefits and challenges of their approach. Gain insight into platform standardization, project instances, user freedom, and agility in content management.

tallys
Télécharger la présentation

Cross-College Collaboration for Web Services Excellence

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. Web Services College of Life Sciences / College of Medicine, Dentistry and Nursing Andrew Millar, Web Services Manager

  2. Web Team • Pre March 2012 • CLS = 2 web posts, CMDN = 1 web post • CLS on Drupal, CMDN on T4 • Very little, if any interaction • Post March 2012 • 4 web posts shared across 2 colleges. • 2 core funded, 2 funded by income. • Cross college collaboration and sharing of best practice.

  3. CLS/CMDN Web Team College Web Team Merger

  4. Core Principles • Mobile first, desktop second. • Create once, deploy many. • Integration not duplication.

  5. Our Approach • The problem • 1 size doesn’t fit all • Best tool doesn’t necessarily scale • Our solution • Standardise on a versatile platform (Drupal) • Instance per project • The Benefits • No danger of new functionality or upgrades breaking existing sites • Users can have as much freedom or restriction as they wish. • Agility • Drawbacks • Lots of individual sites to maintain • Content Sharing

  6. Aegir & Drupal

  7. Aegir & Drupal PLATFORM

  8. Updates ; This file was auto-generated by drush_make core = 7.x api = 2 projects[] = "drupal" ; Modules projects[] = "ctools" projects[] = "cck" projects[] = "context" projects[] = "date" projects[] = "email" projects[] = "features" projects[] = "filefield_sources" projects[] = "link" projects[] = "references" projects[] = "uuid" projects[] = "uuid_features" ; Themes projects[omega][subdir] = "sites/all/themes" • Drush and makefile • drush generate-makefile

  9. Updates Platform 1 Platform 2 Site 1 Site 2 Site 3 Site 4 Site 5

More Related