Mark Boulton on
One of the aspects of this project is design and develop a theme that could be used for all Drupal websites within CERN.
A few months ago, we started gathering the requirements for this theme and auditing the various use-cases across the organisation. It became clear the those use-cases are extremely varied; from department websites, to individual’s blogs. The editorial need is also quite broad; from a communication tool around working groups, to simple note-recording. This theme had to work quite hard in capturing this broad requirement, but also putting in place tools to allow for slight customisation for users to make their site their own.
With this in mind, we established some requirements:
- Provide a design system that feels ‘part of CERN’.
- Provide a number of tightly controlled opportunities for user configuration.
- The theme should adapt to small screens.
Let’s have a look at each of these in turn:
Provide a design system that feels ‘part of CERN’
The theme shares several components with the new CERN public site: Typography, grid and typeface. The typeface shown in these concept mockups is the typeface PT Sans. We’re proposing that this is embedded into the web-page – rather than using Arial or Verdana – as the first typeface choice. PT Sans is a highly legible web font, and through its licencing will be freely available for all users to see without incurring licencing costs.
By using the same typeface, typography hierarchy and grid layout, any site that is created will feel like it belongs to the ‘family’ of CERN websites.
Provide a number of tightly controlled opportunities for user configuration
Through our audit, it became clear that sites need to look different for different use cases, but also need to feel like they belong to one another to retain a family feel and build and reaffirm the CERN brand. Answering the question ‘am I in the right place?’ of the user.
To do this, we needed to make sure there was configuration options open to the user to create the site they wish, and to a certain degree, how they want it to look. There are two ways we could do this:
- Let the users edit the stylesheet themselves
- Give them tools to make changes without knowing code.
We opted for the second.
We’re proposing the user can change the palette of the theme: choosing a blue palette, green, black, grey or whatever predefined palettes we design. Once selected, the system will automatically apply all secondary tones, link colours, type colour etc. Maybe in a future version, we could create over-rides for these so they could be individually altered. But, for this initial release, we’ll be defining palettes.
Of course, the user is still able to define the functionality and placement of content as they build out their site, as they can do now.
The theme should adapt to small screens
Web content is being consumed on an increasingly diverse screen size. In response to this, the website will scale to fit these screen sizes without breaking or degrading the content.
We’re finishing up the first release of this theme in the next few weeks, and aiming to be integrated for a limited beta test in CERN throughout the early part of next year.
Design concepts

Image showing generic theme palette.

Image showing the same basic design structure but a different palette, masthead background image and department logo.

A further concept that shows how the same design system can be made to look fairly different by a predominantly white palette.
- Mark Boulton's blog
- Sign in to post comments
Comments
So far so good
Mark et al,
The decisions made so far set a clear direction. A question from the back seat; how many palettes and use-cases do you think are needed?
I'd suspect that there will be 10-20 palettes (one for each department and each 'big' experiment.) and 5-10 use-cases (which -on customer request and charges- can be -to a limited extend- customized).
What are the thoughts about migration? Will migration tools me available? Do they have to be developed? Is that hand work? Or will the main policy be to let the old stuff fade away?
Happy holidays and a great 2012.
Paul.
Logo should be at the top!
The CERN logo is quite cool and is easily recognized. Thus, from a brand-recognition perspective, it makes no sense to stick it at the bottom of the home page, where it often isn't visible due to window sizes & scrolling. At the top of the page, people are guaranteed to see it. Note thateveryone who knows about web presence has their logos at the *top* of every page (cf. hp.com, oracle.com, ibm.com, wikipedia.org etc.). Please fix this!
Thanks,
-John
CERN logo placement
Thanks for your thoughts, John.
This Drupal theme will be used by all sorts of CERN entities, some of which will be 'more CERN' than others, and some of which will have their own branding identity that is distinct from CERN's. It is with this in mind that we put the CERN logo at the bottom of the page. Take an experiment - ATLAS, for example: ATLAS has its own branding and logo, and if the collaboration were to use this theme they would no doubt want the site to use their own logo and branding elements 'front and centre'.
Branding isn't just about a logo, it's much broader than that and there are a number of other elements that can make a CERN website 'feel' CERN. For instance: URL, typography, language and style. Through developing the new CERN website and this Drupal theme we hope to describe these elements in more detail and provide a complete style guide for developers and content creators that describes underlying user experience baseline for content and visual elements so that websites feel like they are part of the CERN family.
Providing a completely uniform treatment of all pages at CERN - as per the websites you mention - is not possible given our web governance structure. Nor is it necessarily desirable: CERN is a diverse, complex organization, home to a large number of collaborations and partnerships.
One of the key elements that will be used to tie websites together is the grey header bar that you can see in Mark's examples above (bear in mind that this grey bar is by no means final as you see it here). The first thing inside this grey bar is the word 'CERN' and the last element on the page is the CERN logo, the idea being that the entire page is framed by visual, branding and navigational elements that define it as a CERN page while also allowing strong sub-brands to express themselves.
CERN logo placement
I understand the reasoning but can imagine that in the example such as the EN page above they would probably like to see the CERN logo in the banner to the right of EN in the circle. So is CERN logo placement part of the customisations we can use?
Logo placement, systems
Hi Bob,
In the standard theme settings you will be able to choose the logo for your site (e.g. the Engineering logo in this example), but not where the CERN logo fits. In theory, for those with a little know-how and a strong desire to see the logo at the top-right of the page, this would be possible using a sub-theme. However, this area will be tight for space: language switchers, search boxes, navigational elements may all fit there too, and the CERN logo needs a little space around it.
Beyond the theme we are looking at describing a global experience that all CERN websites (Drupal or not) can align with. A pattern library that describes how menus should work, or how to build a slideshow, for example – and how the CERN logo should be treated online. A good example of such a library is the BBC's Global Experience Language: http://www.bbc.co.uk/gel
Essentially we need a system: a set of guidelines founded on design principles that allow us to move away from discussions on what 'looks better' and towards describing a unified user experience across the CERN web.
(Apologies for the slow reply!)
Dan