Tagiwyd gyda

Rhannu

Graham Davies, 20Medi2014

"Content is King". The phrase is strong, infallible, sitting proud on his pedestal, a little like the Queen Mother, or the National Health Service. Sacrosanct. But has the time come to question some of our long held adages in the world of digital content and web design? Is content actually 'King' anymore?

Fresh back from an energising few days with the fab team at Culture24 at the Let's Get Real workshops and conference, I am determined not to let the enthusiasm and momentum get buried by the squillions of things in my inbox that greet me now that I am not 'Out of Office' anymore.

The discussions of the last few days have left me pondering over our constantly evolving digital landscape.

Which direction, and how high do we have to throw our digital content ball to get it successfully into the constantly moving net of engagement?

Jessica Riches, in her talk on 'Learning from Brands' seemed very surprised that she was the first of the day to mention the phrase ‘Content is King’

This made me think. And think again. About the shift in focus to be more about platforms, the importance of audiences and what channels those audiences use and reside in.

So has the time come to update or even rewrite the rulebook?

1. Content is King?

Surely it's not just raw content that is king anymore. Who your content is intended for significantly alters how it should be written and where it should be published. What is the intent of those people reading it? (as apposed to the intentions of those writing it). So I give you rule rewrite number 1:

Content, Intent and Purpose are the new King, Queen and Jack

By thinking of it this way, you are reminded that content on its own doesn't stand any more. It's equally important to also think of why you are writing itand where the people are who want to read it?

2. Build it and They Will Come?

This fell off its pedestal a long time ago, but if we were to prop it back in place the stonemasons would need to re-carve the plinth to read:

Write it and take it to where they are. Or perhaps better still: Go pay them a visit and have a chat

This helps reinforce the idea that we can't be institutional broadcasters anymore, we should be working with our audience to help them answer what they want to know, rather than what we want to tell them.

To demonstrate this, Shelley Bernstein provided us with a superb keynote speech at the Let's Get Real conference on how the Brooklyn Museum are trusting the audience and developing a wholly user-centric approach to their new responsive museum.

3. Design Responsive Websites

Great, Yes, very good. Although a revision of this phrase can encompass web design by default whilst primarily focussing on content:

Optimise your content to be platform independent

4. Think Mobile First

Yes, we must, and we should make this behaviour ingrained. By turning this rule upside-down, our new banner proclaims (and by its very nature automatically assumes mobile first):

Remember to check the desktop

Think back to those good old days where everything had to be retrofitted to work in IE 6. Who now retrospectively checks that everything reads and works well on a desktop? Not many I'm guessing.

But beware. Herein lies the paradox: Remember, people looking to visit one of our venues are more likely to be looking us up through a mobile device. However, people looking at in-depth long-form curatorial and academic material are predominantly still using desktops.

This is where headline metrics can be misleading, if your website as a whole shows a rise in mobile, that doesn't mean that all the content on the site is being accessed through mobiles. This is why metric analysis is so crucial before we apply blanket statements based on overall trends.

This brings me onto to something bigger I have been mulling over recently...

"Can we put it on the website please"?

Quite frankly, I dislike the term "Website". I often ask what section or area people are actually referring to, for websites these days have come to contain many distinct areas and functions, serving completely separate and different audiences and requirements. Maybe this is the crux of the problem? At the moment we are all busy working on a 'one solution fits all approach'. Shouldn't we be thinking of applying separate templates and content strategies based on different audience requirements within our own websites?

Going back to our rewritten rule number one, and this should be applied within (and throughout) our own organisational websites too.

All this can help us ensure that we consistently put the users needs at the centre of our goals and ambitions. Just by thinking a little differently about our assumptions, we have the ability to take a quicker, more direct route to successful engagement.

Tagiwyd gyda

Rhannu

David Thorpe, 12Awst2014

There is an exhibition showing at National Museum Cardiff called: I-Spy…Nature (until April 2015). One of the touch screens (picture 1) focuses on a selection of diverse, interesting and beautiful biological and geological slides from the Museum’s Natural History Collections. This blog is about the small aspects of the touch screen that I was involved with; plain and simple.

Resources & Outlines

One general overview image of 36 slides

12 very high resolution images of some of those slides

27 inch touch screen

Complement an actual Micrarium, which would be displayed neatly above the touch screen

Incorporate a Victoriana style

Target audience: young folk

Flourishes

The high resolution slide images were always the prize, therefore it seemed obvious to sort out the zoom features first. Using the Javascript version of Zoomify (other javascript frameworks are available) gave us a good foundation to work on. We just needed to tap into their Zoomify Javascript code a little, then add our own layer of Javascript and graphical flourishes to make the design fit in with the exhibition outlines.

All the controls were laid out in plain sight, hopefully to reduce any learning curve when approaching the interactive; and since the touch screen is quite large (27 inches) we had the space.

Five additional features were added to the zoom screen (picture 4):

Zoom controls

Navigation controls

Home button

Information button

Change language (English/Welsh)

n.b. where possible I tried to avoid using words to describe button functions, hence why the home button is only an image, but this idea fell down a little when it became clear you couldn’t avoid a word or two to help the visitor work out what specimen they were observing.

Into the Arms of a Microscope

Once or twice someone may have caught me saying things like: “Plagioclase Feldspar” or “Olivine”. Anyhow, part of the fun with looking at slides is the process of selecting a new slide, I thought so anyway - you were never sure what would be on the other side of the glass.

I wanted to avoid the conventional method of changing between images, which is usually to include a ‘next’ and ‘previous’ button; so tried to incorporate some of my vague science memories with a quick reconnaissance mission (picture 5) to see the microscope that was being prepped for the exhibition.

Since there were 36 lower resolution images on the home screen, but twelve high resolution images on the slide selection screen, it gave some space to move a simple microscope stand into view, which provided the excuse to animate the microscope arms and float the slides back and forth. The iris transition between the microscope slide view and the zoom view is loosely based on the idea of looking down a microscope eyepiece.

Intermittent Contact

The interactive was built on HTML and Javascript with animations mainly driven by CSS. Due to the amount of images used in this interactive (up to 120MB), the project was exported from Amgueddfacms CMS into a standalone ZIP file then installed onto the exhibition PC - this improves the interactive response times, since it doesn’t have to wait for any image files to download over a network connection.

We’ve been using Firefox for a while as its platform independent and has neat little add-ons (R-Kiosk and Block Site). In this case, the operating system is Windows 7, with a locked down user account which only has access to Firefox and the touch screen drivers.

Usually we use Google Analytics to record button events, to give us an indication of how much the interactives are being used, but Google Analytics is designed to work with regular domain websites, which is not the case when running locally from simple hard drive files. Therefore the button events are recorded by the web server through AJAX calls.

Thinking about it again, it might be more efficient to store Javascript events in the browser’s HTML5 web storage throughout the day and only send it back to the web server when the computer boots up in the morning. Therefore, only bother the web server once a day, rather than hundreds of times a day.