Presented at DrupalCamp Bristol 2015 as Microserve's Sponsorship Case Study. This 15 minute talk covered the problems and solutions which we found whilst building the 6 Bath Heritage Drupal Websites.

1. Case Study:
The Roman Baths
(in 15 minutes)
www.romanbaths.co.uk

3. ● Won on open tender in collaboration with Torchbox (torchbox.com)
● Sites were previously built using the depreciated Immediacy CMS
● Wanted 5 sites with their own “look and feel”
● Better structure between sites and an improved User Experience
Project Overview

4. What problems did we
face?

5. 1. Client wanted 5 (6) websites within a fixed cost budget
2. Brief required automated migration of content
3. Each site has it’s own content editor(s) who had perception of “tech fear”
The Key Problems

6. Solution 1: Design and
Workflow

7. ● Design and Development covered all features/content types - Roman
Baths was built first
● Pantheon One - “The website management platform for Drupal sites” -
https://pantheon.io - custom distribution
● Features driven development - single SASS base theme
Design and Workflow

8. Solution 2: Enter
GatherContent
“We're the content planning, production and workflow platform that
helps agencies and marketing teams.”

9. ● Create content types - add content - import to Drupal
● Pro’s: Easy to use, gives a good introduction to using Drupal content types
● Con’s: Has trouble dealing with non-simple fields, felt like it was in
development
● Ended up using it as a “halfway tool”
GatherContent

10. Solution 3: Don’t neglect
the admin interface!
“Drupal administration doesn’t have to be confusing!”

12. ● Separate Entities from Nodes and build a simple admin view to include
DraggableViews (because the Entity interface is horrible!)
● Easy module wins - Adminimal theme, Adminimal menu, Administration
Views, CKEditor Link etc.
● Define your own CKEditor (WYSIWYG) styles and limit where necessary
● Limit permissions!
Admin Interface

13. Why did it go so well?

14. ● In-browser design: "It looks just like the design!"
● Promote a healthy editorial team - welcome use of your phone number
● The “80/20 rule” and how to manage requests in a fixed cost project
● Last but not least - a great team!
Summarise

15. Thankyou!
Rick Donohoe
rick@microserve.io