Usability

There has been a lot of informal talk about Drupal’s issue queue. For designers and non-technical people, it can be a confusing place. And while there has also been some talk about creating a separate place to discuss design-related issues (for example), the simple fact is: the issue queue is where developers get informed about problems and requests and that’s the place where they organize the work that they do. If non-developers want to improve the code, they have to use the issue queue.

I am looking for people who are able to do video editing, I have a number of videos that need some title's and minor editing. These are all video recordings of usability testing we have been doing at Baltimore in 2009, we have been able to release three of them but we intend to trow out all of of them - but for that to happen before Drupalcon I will need some help. You can reach me by contact form.

I'm sure many of us have noticed a need for better block management. Or at least, these people have:
http://drupal.org/node/343710, http://drupal.org/node/416002, http://drupal.org/node/197844, http://drupal.org/node/386532

It does get harder to keep the blocks in the right order and to find the one you want to edit as the list grows, but my biggest problem is handling visibility settings.

As a user, here's how I'd expect to use blocks:

I'm posting this because it's so solvable and yet it causes so much grief.

Try to imagine you've never worked with Views before, and you're pretty daring about trying out new software. Like most of us, you're likely to start throwing things around before you've finished reading the documentation.

You go to /admin/build/views and see "storage" "type" "tag" with no explanation. You do see a list of views, and you decide to try playing with one of them to see what happens, so you click on the "edit" link.

Admin UI question to ponder:

Suppose a module adds a property or setting to content types: it allows you to say "content types X, Y, Z have property foo, or can do a particular thing, or do a thing in this particular way".

When should this be a UI element added to the content type admin page, and when should this be a single list of all content types?

A run-down of examples:
Added to the content type admin page: upload, comment, nodeblock, community_tags, meta tags, nodewords, content_profile
List of types: taxonomy, flag, simplenews

Hi everyone,
One annoying thing I found about the drupal website at the beginning is when I would type in a module name in the search box, i.e. "fckeditor" and the main module page would never come up. Everything would be issues or forum topics. I couldn't figure it out till I learned to just go to /project/xxx

The thought came up a couple days ago, during the conversation with Robert Castelo.

We could use our office space in Holborn, Central London. We can have 2 days on Saturday 22nd and Sunday 23rd of August.

Let's focus on improving the user experience on Drupal.

There's no agenda yet.

Your thoughts are welcome!

Currently in Administer>>User Settings you can customize various aspects of user registration, but not, as far as I can see, what the user sees when editing their account information. This would be helpful. Also, depending on the site configuration, there can be a lot of stuff between the top of the page and the "Save" button. Might be nice to have reminders for the user to click "save" when making changes.

As for most of our sites we want to turn revisions on for all content types, a module (or D7 core patch) to do this from somewhere with a single switch (or checkboxes for all content types in one place) would be nice.

Questions:
* Is there already a module that does this, hiding from my searches?
* Should other per-content-type workflow settings also be centralized?
* Where should centralized settings like this live in the administration menu?