Drupal.org – Prototyping commences!

Progress continues apace on the Drupal.org redesign project – thanks to lots of help from you, we have now moved into the rapid prototyping phase.

In the spirit of this open redesign process, you’re more than welcome to take a look at the prototype as it evolves from its current, very sketchy state to … well, whatever it becomes. Hopefully a great home for the Drupal.org community and their product!

Now, be warned – it’s not pretty and it is far from complete. There are some things we kind of like and plenty we think may be a little dodgy, and some stuff that is just holding a place until we have more time to think on it (or to generate a little feedback in the meanwhile). The visual design (colours, fonts, etc.) of the prototype bears not resemblance to what we imagine the finished Drupal.org website will look like. Some of the content we kind of like, a lot of it is just holding text. It is very much a work in progress!

It’s really all about what’s on the page and what it’s called – lots of information architecture to look at really!

Anyway – enough with the disclaimers – why don’t you go take a look for yourself and, if you’re so inclined, leave any feedback or questions you have in the comments here and it will go into the mix for the next iteration. I’ll let you know when the next version is up for you to take a look, and we’ll continue like that for the next few weeks at least, as we gradually build in all the content and functionality and fine tune the content and interaction.

Drupal.org Prototype Development – Iteration 2

Drupal.org – What we learned from the Community Wireframing Project


I thought you might be interested to know a little about what we did with all the wireframes people submitted for the Drupal Redesign Project.

Around 30 wireframes were submitted, mostly to the Flickr group, but also on Drupal Groups and other locations (linked to in the comments of the original post). I think this is a really great effort and I am really pleased with the participation in the project.

It wasn’t just a fun exercise though, so since receiving the wireframes I’ve been doing a little work to try to understand what this exercise can tell us. In order to do so, I’ve been making a page for each template that people chose to tackle and then making a little sticky note for each piece of content/functionality or concept that people included on their wireframes and tracking how many times an idea was included. 

This process helps us to confirm a) which templates people are thinking about most (the homepage (predictably), community, support, project and documentation type templates were most common), and also b) what kinds of content they expect to be able to find on that template.

The results are certainly not a prescription for which templates we design and what goes on them, but it is a useful input to the process, particularly as a cross-check – to make sure that the ideas we are suggesting aren’t omitting anything important, and that we have considered all of the ideas generated from this exercise in the process of working on the wireframes and prototype.

Most excitingly, though, we hope that this exercise has helped to encourage more thinking about what the new Drupal.org can be, and to trigger some really interesting conversations – in particular some great ongoing discussions around the project page, and integrating groups and projects over in the Redesign Group.

Don’t feel that you have to stop now though – drawing things out is a great way to communicate your thoughts and give us feedback (can save a thousand words, so they say) – if you’ve got an idea or something you’d like to share, feel free to run up your own wireframe – pen and paper is fine! – and post it either to the Flickr group, or your blog, or to the Redesign Group, and let’s talk about it!

Drupal.org – more thoughts on the Information Architecture (Part 1 – Projects, Downloads etc.)

Thanks to everyone who gave feedback on my initial thoughts on the information architecture – it was certainly food for thought and, as a result of that and some more work on our part, we’ve moved on a little in our thinking – I’d like to share some thoughts and some questions with you now, for your consideration.


In my previous post I suggested that perhaps two different faces on essentially the same content could be valuable – one being ‘download’ which would be used by people who were using Drupal as a tool and looking for the core, modules and themes to download and use, and one being ‘Project’ which was targeted at developers involved in further developing and, of course, maintaining Drupal, the project.

After hearing all the feedback to this, I now agree that this is not a great idea – in a nutshell because, as you have said, we don’t want to create such a void between using Drupal and contributing. Also, given that we have a ‘getting started’ page, people who are less familiar with Drupal will be directed there, and from that section they can be given an easy guide to what to download and from where.

So, based on your feedback to date, let’s remove ‘Downloads’ as a section or sub-site.

Information Scent for Core/Modules/Themes/Translations: I’m thinking of a word that is *like* ‘Project’ but makes sense to ‘outsiders’

That leads me to one of the reasons I suggested ‘Downloads’ in the first place – being that ‘Project’ is a very ‘Drupal’ word. To someone who is versed in Drupal-speak, ‘Projects’ means ‘things that we’re working on, like the Core project, Modules, Themes, and even Translations/Localisation. But for someone who is NOT Drupal-speak-savvy, ‘Projects’ or even ‘The Drupal Project’ is not good information scent for really important (perhaps some of the most important) content on the site.

Non-Drupal-speak-savvy people will not look under ‘Projects’ for Downloading Drupal, Modules, Themes or Translations… so we need to come up with a label for this part of the site that makes sense to everyone. (Or, at least, gives them a clue of what might be contained within, sends them in the right direction).

The card sorting exercise gives us the following insight:

  • When asked to categorise ‘Contributed Modules’ participants who identified as ‘outsiders’ used terms like ‘Development/Developers’ and ‘Downloads’. 
  • When asked to categorise ‘Themes’ participants who identified as ‘outsiders’ used terms like ‘Designers’ and ‘Downloads’. 
  • When asked to categorise ‘Translations’ participants who identified as ‘outsiders’ used terms like ‘About Drupal’ and ‘Developing’ 
Now, we know that we don’t want to use ‘Downloads’ because it doesn’t reveal the ongoing project work and encourage participation. I have given quite a bit of thought to creating ‘Developer’ and ‘Designer’ sections and splitting content off that way, but my gut feeling is that is a highway to pain – primarily because both the content and audience are rarely clearly divided into one of these categories – I imagine there would be an awful lot of crossover – and also because it seems unnecessary (and less than ideal) to divide the Drupal community by role.
That leaves us with the enormous question of – what do we call the section currently called ‘Download’ (on the Drupal website) and ‘The Drupal Project’ (on our proposed IA), from which the Core project, Modules, Themes and Translations can be accessed. It’s got me stumped for the moment, so I’d love it if you can throw some ideas at me. 
Or perhaps the whole idea of having one section to house all of this is the problem, and we need to expose the contents of this section at a higher level?
Any thoughts you have on removing the ‘Downloads’ subsite and re-naming ‘The Drupal Project’ sub-site would be most welcome! (Insiders and outsiders both!) :)

Drupal.org – what makes up Drupal.org Community?

I’m going to call on your expertise again to help me think through an issue for the Drupal.org redesign. This time we’re thinking about community.drupal.org, which is theoretically the community ‘hub’ of drupal.org.

At the time I proposed it, I imagined it being a place where both Groups and Forums would live and potentially also Planet Drupal and other community type ‘stuff’. Now that we’re starting to get into prototyping (yes, you’ll see it very soon!), the devil, of course, emerges in the detail…

The major part of Forums is – at least to my eyes – support. That being the case, putting it under a ‘Community’ label is not the clearest way to direct people to this support.

Other (apparently less important) content in the forums includes News & Announcements, General Discussion, Drupal Showcase, Events and Paid Drupal Services. Now, short of ‘General Discussion’ each of these other items have natural homes in the proposed new IA.

I’m also aware that there is a very active ‘groups’ section who have all manner of discussions going on (and, perhaps, quite a bit of duplication with forums?)

So, here is what I’m thinking… what if we pull forums apart a little. We *might* rename ‘Documentation’ to ‘Documentation & Support’ and include the support forum topics there. And we might retire the forum topics that are now duplicated in the main information architecture (paid services, news, events etc.). We might keep the ‘general discussion’ forum in Community, because it seems like a good idea to keep a nice ‘light weight’ place for all kinds of topics to be discussed, but the bulk of the Communities section would be groups.

The more we work on this project, the more obvious it becomes that Drupal.org is, in its entirety, a community site – so in our context, what does a ‘community’ section mean? I’m thinking that it means a place where the *topic* is more about the Drupal Community than it is the about the Drupal Project. But also that we want to intertwine these two much more than they are at the moment, so contextual linking is also going to be important.

How does that all sound to you?