One thing I’ve learned on this project so far is that if you’ve been using Drupal for more than about ten minutes, chances are you’ve had a look for a module or two.
Research participants are rarely unanimous but I think I can safely say that every single Drupal user I have spoken to has told me how difficult it is to firstly find and then evaluate the usefulness of modules.
So. That’s one thing we’d really like to help to fix in this redesign.
In the latest iteration, you can see where we’ve gotten to so far with the modules landing page – it’s a start but it doesn’t really begin to address the really difficult questions which are:
how do people look for modules? and
how do we design the interface and information architecture so that people can find the module they need?
most advanced users will use Google search to find a module on Drupal,org using keywords that they think are likely to be in the module name
advanced users refinding a known module are likely to use the URL (remembered or bookmarked) to get to the module page
everyone finds it difficult to find a module from the current list of categories
in some cases, the category names are not sufficiently descriptive or specific to be very helpful (3rd party integration is an example of this I think)
in some cases, the category names are in ‘drupal-ese’ and meaningless to new users (new users don’t know what CCK is, or what Organic Groups are)
modules can live in more than one category (this is not a bad thing)
you can only order modules by category, date or name (check this)
it is difficult to distinguish between a ‘big’ or important module ad a small, very specific module
categorisation is very much about what a module actually does, rather than what you can do with it (for example, to use an example given to me the other day, if you’re looking for a module that will let you do listings for an estate agents site what module do you want?)
Here’s what I’m thinking
we need to better support people’s desire to search for modules (hence the emphasis on search on the homepage and the associated massive improvements to the search capabilities of search for this site when it is relaunched)
we need different ways to ‘cut through’ the modules to support different scenarios such as: I’m new to Drupal and I want to know which are the most important modules, or I’m building a site for an estate agent and I want to know what module would be best for making property listings, or I want a module that will automatically resize images depending on where I put them in my news site.
we *could* try to do this with a controlled vocabulary, but would we ever be able to agree on what it should be. Unfortunately, I don’t have the time on this project to be able to complete it, and I suspect it would be extremely challenging to undertake this task as a community…
we *could* harness the scale and diversity of the community and focus more on tagging in a less structured, more Folksonomic way – but this isn’t going to help guide people through the scenarios that need more support as outlined above…
we probably need to do a combination of the two – with some broad, fixed ‘structural’ categories, and categories that go beyond just describing an aspect of what the module does or how it does it, supplemented with community driven tagging, to help enhance the findability via search and possibly generate new additions to the controlled vocab.
So, assuming you’re with me on this (and that’s quite an assumption I know) – here’s what I need some help with… I could really do with some help compiling some list(s) of categories that would help people find modules in the usage scenarios I’ve suggested above. Also, if there are other important scenarios I’ve missed please let me know!
We should probably do this on a wiki, or something similar. But perhaps lets start with some ideas here and I can compile them into something more comprehensive.
Anyone got any thoughts on this? (Don’t feel you need to be comprehensive)
We’re both excited and nervous to show you this latest version because we’ve taken a bit of a deviation from our previous path as a result of both feedback from you and usability testing, and us not being quite satisfied with the work that had been done so far.
There were a couple of things that were really bugging us in the versions up to now. In particular, the navigation in the header (there was so much of it and it looked kind of messy and confusing and in tests, we observed that people completely ignored it!). The Logged In version of the homepage was a good idea but the execution was coming up short as we learned that ‘hard core’ Drupallers thought it was a v valuable addition to the site but just about everyone else wasn’t interested…
A behaviour which we have observed since the very early days on this project has the use of search – lots of people use search lots of the time, and a lot of the tasks that the site has to support are heavily search oriented (finding modules, finding help etc.). Drupal.org users have some of the most advanced Google skills I’ve ever observed! – and yet up until now, the redesign of the site didn’t really pay this much heed – it was still very much a hierarchical site made up of silos of content… forcing people to choose between this section or that to find the content they required. Another thing that we had largely ignored is the use of URLs as shortcuts to information (eg api.drupal.org to get direct to the api documentation site)
(Having said that, I am very pleased that the information architecture has actually performed well in task based testing - with a few exceptions like, say, ‘Professional Services’ which was too limited for the content it needed to hold and has now been changed to ‘Commercial Services’ (you like?))
So, as a result of these issues, we’ve made some fairly significant changes to the homepage and navigation structures, placing a much greater emphasis on the search behaviour from the homepage (and throughout the site), and significantly simplifying the ‘header’ navigation. Early participants in the crowdsourced wireframing exercise may also be pleased to see the inclusion of the ‘big ass footer’ (refer to some early posts on the Flickr group if you have no idea what this refers to!)
We did some initial usability testing showing a more ‘search’ based alternative earlier this week and it was quite well received – since then we’ve done quite a bit more work on it.
There is one important thing that has been missed in this version (which hopefully Mark will be able to get sorted tomorrow!) which is that the search refinements (modules, themes, documentation and forum posts) will be links direct to a ‘landing page’ for those sections to better support a browsing interaction style).
The ‘logged in homepage’ has evolved to a ‘dashboard’ which we hope will be more useful to a broader audience whilst still supporting the needs of the ‘hard core drupaller’. The idea would be that you could set whether you see your dashboard or the standard homepage as the default when you visit the site.
There are a whole range of changes and updates and additions, I won’t go through all of them here, rather, dive in and take a look for yourself. I’d really encourage you, as you do so, to think not only about ‘how do I like the look of this‘ but also think ‘how do I use the Drupal.org website now (or how would I?), and how would I do what I want to do on *this* version of the site?’
I do want to give a little more feedback on what we’ve learned from usability testing which explains the high priority and size of the ‘case study’ on the homepage. With virtually everyone that I have interviewed so far, almost without fail one of the most valuable pieces of content (not including modules etc.) is the case study – this is true both for ‘outsiders’ who are evaluating Drupal, but also for ‘insiders’ who are on the learning curve – the case study is a great opportunity for us to challenge the perception of what a Drupal site looks like, to showcase some of the great companies and organisation who use Drupal, to explain more about how Drupal sites are built, what modules were used, the team that is involved, any challenges and learnings along the way – in short – they are really very productive and impressive for a large group of our audience. As I said to Mark recently – I cannot overstate how valuable case studies are to the people I have met and talked to about the Drupal.org website – hence their very prominent position on the site.
We still have a lot of work to do – in particular, I’m hoping that we can make some good progress in the ‘documentation’ section and the modules and themes pages. These are very important parts of the site and what you see there at the moment doesn’t reflect our current thinking on how it should work (which has been influenced and inspired by listening to the community talk about what they need and what they’d like to see!). The community landing page is still very much up for grabs (needs more thought and love and doesn’t really reflect our current thinking).
Please go in and take a look and let us know what you think – show your friends and tell us what they think, and consider getting involved in our crowdsourced usability testing if that takes your fancy.
This week I’d really like to invite people to do some usability testing comparing the previous (iteration 6) homepage with this one to get some feedback on this new direction.
Please feel free to post any feedback here, or there is also a discussion over on groups.drupal.org if you’d like to join in over there. I look forward to talking with you about this some more!
(UPDATED!) Iteration six is now live here. I’d like to encourage you to take part in our Crowdsourced Usability Testing Campaign by doing a few tests yourself, wherever you are in the world, and contributing your findings back to the project.
Here’s what you need to do:
Find some participants to take part – we want a mix of people along the spectrum of Drupal involvement from those who don’t know much to those who know lots and are super involved. Some tips for recruiting can be found here (feel free to add any other tips you have to our wiki!)
Work out a way to record your interview – some ideas here. Personally, I’ve found remote testing more hassle than it’s worth and much prefer to do in person interviewing. My technology of choice is a MacBook with Silverback installed for audio and video recording (you can get a 30 day trial for free).
Do your interviews!
Share your interviews and findings! I’ve been exporting and posting some interviews on Vimeo, which is my preferred video sharing site. You can put yours wherever you like, just link to them from the comments of this post once they’re posted (and/or add them to the wiki where mine are now) – if you have some time to write up what you’ve learned as a result of the testing that would be fantastic! (If not, don’t worry, we’ll take a look through the video ourselves!)
That’s it! Not so hard at all, is it!
If you have any questions at all, post them here (no matter how silly they may sound, chances are others have exactly the same question or it’s something I forgot to cover in this post or on the wiki!) – I or someone else helpful will get back to you ASAP.
This is a great opportunity to help out with the Drupal project and a great chance to get some usability testing experience under your belt – which is a really fantastic skill to have, whatever aspect of design or development you’re most into. I really encourage you to give it a try and look forward to seeing what you come up with! I’ll be sharing my videos as soon as I can export them after usability testing sessions on Monday 3/11
If you’re able to do some testing early next week and post your feedback mid-late next week that would be fantastic. If this schedule doesn’t work for you – don’t fret – more iterations are coming hot on the heels of this one and more testing will be required and welcomed! You can get involved in the next few weeks if that suits you better.
You’re going to be hearing more and more about usability testing in the coming weeks! As you know, we’ve been including Drupal.org users in the redesign process from before the first wireframe was sketched, and we continue to include both ‘insiders’ and ‘outsiders’ in the process – currently in the form of usability testing the prototypes as it moves from iteration to iteration.
We recently conducted some tests at the Web 2.0 Expo in Berlin which allowed us to talk to a bunch of European Drupal Users (and non-users too!). Now we’d like to do some usability testing in London (where I’m based).
If you’re in London on Monday 3 November and would like to participate – please email me [email protected] and let me know where you will be (I can meet you somewhere convenient) and when would suit you. I’ll need around 30-40mins of your time.
I’m looking for a mix of people who know a *lot* about Drupal (and are involved in the community) through to people who know not much about Drupal but who have some interest in content management systems for websites – whether for your own blog perhaps, or for a company or organisation you’re affiliated with.
Unfortunately, we don’t have any cash incentives for this project, but you will receive much gratitude and lots of good karma for helping build good user experience into an open source project.
My name is Leisa Reichelt. I am the Head of User Research at the Government Digital Service in the Cabinet Office.
I lead a team of great researchers who work in agile, multidisciplinary digital teams to help continuously connect the people who design products with the people who will use them and support experimentation and ongoing learning in product design.
If you're interested in working with me or would like to talk more please email me