Describe the Project (Goals, Requirements, and Outcome):
Mosaic Science is a new popular science ezine that specialises in producing regular long-form articles of around 5,000 words plus images, slideshows, and associated content. The goal of the project was to build this in Drupal 7 ensuring that its output corresponded precisely with a set of design patterns and markup that ensured it worked perfectly on smart phone and tablet as well as desktop. In addition, our team worked closely with an in-house team that was completely new to Drupal with an aim to make that team capable of transitioning other Wellcome Trust sites to Drupal.
As the site is based on long single page articles, performance was also a major requirement, particularly as it's expected that people will be using the site when on the move.
The final requirement was to provide an edit interface that would make it easy for editorial staff to write, moderate, and administer content.
The site launched in February to great acclaim. Its content - all provided under creative commons - has been widely re-used by amongst others the BBC, The Guardian, Huffington Post, and CNN.
Why Drupal Was Chosen:
The client chose Drupal because they wanted to shift to a new CMS and used this project to test Drupal as a potential replacement for their legacy system.
Key Modules, Theme, and Distribution Used:
Panels, Views, Semantic Views, Entity reference, inline entity form, wysiwyg fields, entity_view_modes, workbench, workbench moderation
Why these Modules, Theme, and Distribution were Chosen:
We use a customised version of Semantic Panels called Planer to strip out unwanted markup and inject the markup we had to use to get Drupal to output exactly in line with the pre-built design patterns, which were produced by designers with no knowledge of Drupal. Wysiwyg Fields in conjunction with custom fields so that editors can drop things like slideshows, glossary items, and related content into a wysiwyg editor. That makes it possible for editors to do almost all their content production within a single wysiwyg rather than having to fill out lots of separate fields. The entire workflow model is driven by Workbench, which really ought to make it into Drupal core at some point.