Usability

(or how to reduce a module's functionality)

During it's lifetime a contributed module's functionality expands, which often leads to a module packed with features. This growth of features is common for all software, but for Open Source the rate of expansion seems even higher. Feature rich software may be beneficial to the user but it comes at a price. Usability often suffers.

Forget about the user. There is no average user. "The User" does not exist. There are different users, with different goals, different backgrounds and different levels of experience.

How about thinking about this.
Garland has had its time, and it starts to really hurt my eye.
Sure going for a recolorable theme is a given necessity.

I opt for Pixture, as I see it is very popular, and also because it looks "Joomly" (this may be a reason for people to NOT use it, I know ;) )
In is actual edition it has layout tables, but I'm working on this flaw with someone. Sure I'm not totally out of hunger for personal fame, but more importantly this would get away from the "Drupal looks like Garland" opinion.

Maybe this is already discussed and I'm only missing it?

Hello,

I am a Summer of Code student working on a project called Embed Widgets (http://drupal.org/project/embed_widgets). It allows widgets to be created from Drupal content such as nodes, blocks, or views. Content must first be added as a "widget source" before it can be embedded in a widget. Widgets can be embedded in various formats such as IFrames and Google Gadgets, with more to come.

My project is going great and is nearly complete, but one concern I have is the user interface. I am looking for ways to improve it.

I think it's time taxonomy module got some more love in core. Drag and drop etc. was nice to get in D6, but there's much more we could do. Also I keep seeing various taxonomy administration helper modules cropping up - which is good, but there's no core patches cropping up alongside them, which is a shame, so I'm starting this in the hope of generating some discussion about things we could do this release cycle.

There's three obvious areas where Taxonomy could use some help.

Administration:

Merging terms.
Moving terms between vocabularies.
Mass operations (delete, edit).

The Drupalcon Track "Showcases, User Experience and Design" is still taking Session proposals.

It would be great to have more Presentations on UX Matters. Drupalcon is a wonderful Opportunity to contibute to the topic and maybe get more People on it, as targeted in the proposed Usability Sprint
Anything that touches the Topic UX is welcome. Following the discussions here there is no shortage.

Story to Article seems to have been a good move (and people who haven't tried out a new D6 yet keep suggesting it again all over the place).

However page is still there, and according to both UMN and UB testing, causes conceptual problems for a lot of people.

I took a quick look at wordpress - which has 'posts' and 'pages', here's what they've got to say for themselves:

http://codex.wordpress.org/Pages

There's also a slightly dusty patch here to rewrite the descriptions (again): http://drupal.org/node/233200 and which I'm planning to resurrect.

There are numerous usability issues centred around the administration of nodes. Of particular interest in this discussion is the admin/content/node page. The aim of the discussion is to identify the problems, propose solutions and then break those solutions down into specific tasks that we can put into the issue queue.

The discussion really began at http://groups.drupal.org/node/12507#comment-40213, and so the points made there are summarised below. (An issue has also been created at http://drupal.org/node/270912, but we will probably have to implement several issues to fix this.)