Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to IWMW 2017 - Oxford Mosaic - A Web Publishing Platform for the Future
Similar to IWMW 2017 - Oxford Mosaic - A Web Publishing Platform for the Future (20)
Recently uploaded
Recently uploaded (20)
IWMW 2017 - Oxford Mosaic - A Web Publishing Platform for the Future
- 1. Mosaic website platform how we built a successful service
- 2. What is Mosaic? Simple but flexible • New websites are quick and easy to provision and build • Flexible build options so websites can be tailored as needed Secure and reliable • Hosted in the Acquia Cloud with 24x7 support • Quick response to critical security issues High quality but cost effective • Modern, high quality, fully responsive designs • Websites are cost-effective to build and support Shared and continually evolving • Evolving platform delivering ongoing improvements
- 3. why? • Information Security • Money
- 4. Information Security 110 University websites built per year between 2012 to 2016 16 are built internally by IT Services 400 new websites needing security patching by 3rd parties
- 5. Money Typical build cost of a new website is £20k each That’s around £2m per year leaving the organisation
- 6. the journey • Pilot • Preview • Service • Re-architecture
- 7. Asked for £100k to build a pilot Spent as much of the budget as possible on end user functionality Adopted an agile methodology so when we ran out of money it worked ThePilot Filled our 15 site capacity in the first 6 weeks Extended capacity to 30 sites and filled these within 10 weeks Very good feedback from users on ease of use
- 8. The Product Pilot Issues Lack of design and layout options. Underlying architecture not scalable long term Agile feature management, but limited agile software engineering. Preview Improvements Moved from Trello to Visual Studio Team Services then automated deployment and testing. Core re-architecture from multisite to multitenant. Widget based page infrastructure enabling configurable page layouts.
- 9. Establishing a “Service” Customer Success Analyst Website and guides Taught training course Cost and revenue model Charging process Governance process
- 10. Re-architecture 1st Release version built in partnership with Humanities Departments Driven by the Ashmolean public website Never right first time, or second time Feature Flags to canary release features
- 12. other stuff • How it works • How we work
- 13. Hosted with Acquia • Multitenancy • Page Layouts • Widget Infrastructure • Dynamic Content • Fonts and Colours
- 14. Multitenancy
- 15. Page Layouts
- 16. Layout Widgets and Item Styles
- 17. Dynamic Content
- 18. Colour and Font Configuration
- 19. • Backlog management • Manual test management • Defect Tracking • Continuous Integration • Automate Testing • Automated Deployment • Release Management
- 20. Team Dashboard
- 21. Project Tracking Two week sprints of 8 elapsed days Weekly backlog refinement Regular retrospectives Release to prod after each sprint Decoupled deployment from release Dev and Release branches
Editor's Notes
- Introductions IT Services UoO
- Varying level of competence is managing and securing sites
- Supporting a large number of digital agencies in Oxford.
- Started May 2015 – running for 2 years A complex product that we’ve built in stages Developed a Service in parallel
- Opportunistic and short-term, testing out functionality rather than longevity or scalability. Deliver as much functionality as possible for the money and see what the uptake would be. Delivered in shippable product increments
- Insufficient flexibility to provide for the range of use cases and wide user base. Preset layouts for every content type and limited number of types. Preset homepage with just the option to turn elements on/off No automated deployment or testing. Not a focus on extensible software architecture.
- Developed alongside the Preview Proactive rather than reactive support, especially for onboarding stage Cracking governance issues was essential to the adoption: built a site setup approval system Excellent Sponsor acting as partner, in the right position to influence and convince Took much longer than expected, but critical to success of the product and platform Uptake continues to be high: >100 sites provisioned in 1st year. Some user groups take more work than others High-level strategic support from CIO in both project and service stages.
- Initial build ‘biased’ to departmental use cases – needed extending for high quality presentational requirements of GLAM units Improvement process whether features or architecture never stops: extensions require rearchitecting. Aggressively remove features when adding new ones so that don’t end up with bloated cruft. Get software live as soon as possible and build it in the way that makes it possible to work with there. Productions systems can’t be untouchable. Critical to figure out how to change the wheels on a moving car. => Feature Flags. Temporary configuration to release new features to early adopters and test out with a limited set of users
- Here’s some we built earlier Different look and feel Different use cases Responsive designs: tablet and mobile Cross institution – driver for uptake (Brunel, OU) Grand Union Doctoral Training Partnership
- Pilot was Drupal multi site developed as a Drupal Distribution as we considered Acquia Site Factory But ultimlatley made it multitenancy with Organic groups because of hosting costs also helped content shareing, shared data and security patching and maintenance
- Added page layouts using Paragraphs Widget (which are implemented as paragraphs containing functionality) added to Regions. WYSIWYG, listing, carousels etc, image gallery Can be save as templates and associated with a content type Users can defined their own content types based on core Data Types such as Person, Event, Article, Generic Page
- Widget are based on the layout of the content, eg Banner, Slideshow, List, Grid, Carousel