The sprint will be held at One Shoe http://www.oneshoe.nl/ in downtown utrecht which is one of the largest Drupal developing companies in holland. We have space for 20+ people in their nice and spacious office. Utrecht has lots of opportunities to go out in the evening, and with the Drupal Jam on Friday, this is bound to rock for all attendants.

Starting time will be at 10:00 in the morning on both days.

All people that care for UX are welcome. We can use: Graphic Designers, Coders, Copy Writers, Themers and CSS Ninjas

Confirmed Participants so far:

hey all,

I've (not so) recently published two videos on how I intend to make D7 easier on the newbies.

I focus on two key aspects: getting Drupal up and running and making Drupal look like your own.

though they have been viewed a few times now - and tagged accordingly, I hope - it had slipped my mind to divulge them here ¬¬

I hope this post helps foster some much-needed discussion on my wireframes. I mean, it's not that I didn't show mom and she thought they looked nice, but I need some unbiased, professional second opinions. LOL

so here's the links:

Drupal seems to not really like the notion of containment.
While I appreciate the "sea of node" approach as a base view on content that is structured by taxonomy, I think drupal carries it way too far.
And it means that with containment Drupal reject Context.
And a lots of usability issues stems from that.
A few come to my mind (and I am sure there is many more):
* Where did my content go ?,
* What can I add there ? (What can I do next)
* How do I start something
* My content appears in incontrollable place

I will try to illustrate my point with an example :

This wiki page evolved from the expanded default install profile page. If you have your own description of what Drupal should be out of the box, please add a link to that wiki page. Please also use a format similar to the one described here, it will make it easier for us to translate directly into an install profile. Please DO make edits / updates directly to this profile if you feel that community in a box is what Drupal should do out of the box.

Community in a Box

A community site with front page articles, a community blogging section, discussion forums, and shared image galleries.

Anyone is welcome to sign up for an account and participate in the forums. After some time in the forums, users are invited to become contributors, and can post blog posts and photos, as well as submit unpublished articles.

The blogging functionality is a community multi user blog. It is not meant as one users blog, but rather a large community that can post quick thoughts responding to each other and sharing their ideas. (Note: this is in here because people get confused about "blog" functionality -- this is meant to highlight that having a community blog is not the same as a single user blog, so don't expect to be able to change titles and designs etc. -- your blog posts are in a shared, community space)

Editors are around and police the forums, as well as reviewing and publishing articles and other material for the front page.

The photo galleries are shared galleries: like the forum and the community blogs, users upload them to share, rather than in their own space. There are weekly suggestions for new gallery categories, and users can also tag photos with whatever they like to mix and match how the photos are grouped.

We've just added a new video to the YouTube Channel which we refer to in this post - check it out now:
http://www.youtube.com/watch?v=ShBPEL_ckJw

Over the past week or so Mark and I have been working out the details that go on the panels of the Audience Matrix that we shared with you last week (http://www.disambiguity.com/understanding-our-audience-part-1-drupal7-ux...) (or dress-up-doll document as it has otherwise been named). We’ve made a few changes and added a bunch of definitions.

Here’s what we’ve come up with so far:

ROLES:

You may have heard the excellent and very exciting news that following on from our work on Drupal.org, Mark Boulton Design has been contracted to take a look at the User Experience for the upcoming Drupal 7, and I'm very happy to be working with him on this project as well.

We've spent quite a bit of time trying to develop a framework to understand and frame the Drupal7 Audience in such a way as we can successfully design for them. We thought you might be interested in seeing some of our thinking to date, so we recorded a quick chat about it in this video: http://www.youtube.com/watch?v=_Al-0nUNARc
(I really should do my hair before videoing myself!)

As an overview, here is the outline of what we're thinking:

One of the design directions we are considering involves understanding the key (core) tasks for Drupal users. In order to progress down this path, we need to compile a list of tasks to ensure that nothing important is overlooked.

Please help us compile a list of tasks grouped into priority (high to low). If the task is only performed by a certain 'role' of user it would be helpful to note that as well.

I've kicked off by copying the task list used in the recent usability testing - please add/edit/comment as you see fit!

thanks in advance for your help with this!

At Drupalcon 2009 in Washington, the Drupal design community were asked to become active participants in contributing feedback to the Drupal project.

mfer was kind enough to give members of the Design for Drupal (D4D) Group a tour of how we could provide feedback through the Issue Queue. As a matter of fact, we were shown a version of the issue queue in which any project could be flagged as "needs design review".