This document discusses plans to move the University's websites to a more collaborative framework. It outlines the current siloed systems with separate infrastructure for different parts of the University. The proposed framework would involve more shared infrastructure, centralized training and support, and local development that feeds into the central system. This would help eliminate duplicate efforts and allow direct user feedback. Next steps include mapping areas of focus, securing funding, engaging stakeholders, and continuing to work in an open and collaborative way.
2. IS LTW Website & Communications
• University Website
• University Web Search
• User Training & Support
• Community Management
• UX & Digital Strategy Consultancy &
Research
• Technical Solutions Implementation
3. What we ‘re trying to get away from
IS Polopoly Service
UWP-led, centrally
managed website
framework
IS Drupal Service
Unit
X
Event
Y
Project
Z
Other Platforms &
Services
Scho
ol
B
Scho
ol
A
Institute
C
4. University Website (EdWeb)
• Front-end (http://www.ed.ac.uk)
• Back-end Web Content Management
System
• EdWeb Distribution
• Powered by Drupal
• EdWeb Change Management (CAB)
5. EdGEL
• Digital Design Framework, similar to
http://www.bbc.co.uk/gel
• Sets standards for
– Graphic Design Elements
– Enterprise-level Branding
– UX
– Accessibility
– Technical delivery
• Powered by Twitter Bootstrap
6. What we had planned for
Central Infrastructure
IS-led,
centrally
managed
website
framework
Local Infrastructure
Colleg
e
Z
Supported EdWeb
Core
Sch
ool
B
Local Code
Development
Central Training & Support Local Training & Support
Central User Administration Local User Administration
EdGEL Local Theming & Styling
EdWeb
Distribution
Unit
X
Event
Y
Sch
ool
A
7. What if…
– There was a public service road map to help people identify the future?
– Service/College/School feature prioritisation could feed into a master list
of prioritised requirements?
– System enhancement costs could be shared in all parts of the University?
– There were clear change processes allowing direct user feedback?
– Developers could code locally to feed into the central system?
– We shared knowledge & experience?
– We stopped resolving issues in isolation, eliminating duplicate effort?
– Move away from our silos and work together?
11. EdWeb Code Sprint
• Sprinting towards
a new goal (blog post):
http://edin.ac/2bLX3hr
12. Next steps
• Map areas of focus
• Service-led
• Community-led
• Secure funding (always helpful)
• Engage relevant stakeholders to pilot processes
• Continue to think/act/plan in the same way…
• Being open & review often
