Come discuss, create and plan great Drupal UX design in here!
In discussing the question of inserting a tabindex to create an auto focus for certain pages (/user*, /node/add*, node/*/edit) so that the cursor is always sitting in the first field of the event in question, v suggested that this was more of a usability issue than an accessibility one. I recorded a friend with mobility challenges trying to create an account for those who want some understanding of how important this could be.Read more
We've just added a new video to the YouTube Channel which we refer to in this post - check it out now:
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:
I joined the Drupal community 3 years ago and it has been instrumental in helping me to stay up to date with the latest web trends / developments. Since about 1 year, I've been using Drupal to teach my web engineering students interaction design and information architecture in a practical, hands-on way, by building prototypes with Drupal.
In my opinion, the best kept secret about Drupal is that its power is not so much the technology - a web content management framework. The power lies in the community. Unfortunately, there is still somewhat a divide between designers and developers.
Drupallers, take note of the Interaction Design community (IxDA)! If you haven't already.
I joined the ixda mailing list 3 years ago and it has contributed immensely to my personal growth as an interaction design practitioner. The in-depth design discussions in this community are a true treasure trove.
However, even with 10'000 members, I consider it still somewhat one of the internet's "best kept secrets". IMHO, the current website doesn't succeed well in representing the power of this community. Just recently, IxDA announced plans to re-launch the ixda.org website using Drupal. See Dries Buytaert's blog post about it.
There has been some talk recently at ixda about "open source user experience" and collaborating with the open source movement and learning from each other. I think this is a fantastic opportunity just waiting to happen!Read more
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.Read more
There is a discussion at http://groups.drupal.org/node/19171 regarding revamping the administrative menu. It seems to me that the issue of the improving the menu INTERFACE is different than the issue of STRUCTURE. Here, I'd like to see if we can gather the discussion of practical alternative menu interfaces for core. As I mentioned in the aforementioned thread, please let me know if I'm duplicating efforts here.Read more
I compiled a Yahoo Pipe what collects Drupal UX-related posts from Drupal Planet, Twitter, this group and d7ux group. It's available here:
http://pipes.yahoo.com/pipes/pipe.info?_id=dNbdZy8L3hGbZFW9Pm7D0g (click "List" tab to make a list), it's also available as RSS: http://pipes.yahoo.com/pipes/pipe.run?_id=dNbdZy8L3hGbZFW9Pm7D0g&_render...
Anybody up for maintaining and upgrading it? As I am constantly on and off with Drupal it would be a pain to see this thing is not properly cared.Read more
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".Read more
I would love to be contributing a lot more to the Drupal Usability community, especially in the implementation of prototypes, and solutions to usability issues. However I'm pretty limited by the need to make a living.
Several people here in the community work heavily on Drupal Usability, and appear to do so under company time. How did you convince your employers to invest in Drupal Usability?
I have been dealing with clients from multiple Drupal websites today and found myself wishing for the following interface for my clients. Maybe this is something worth pursuing. At least we have a visual to get the discussion started. I've attached the .PSD file and used the icons from the free library found here.
(I hope the img tag works. If not, click on the attached png.)
Hi guys -
I wasn't sure where to post this (originally asked in the d.o webmaster queue - was pointed to the uxteam group, however I'm not able to access it). Hopefully someone here will know the right person to look at this suggestion.Read more
Changed shortname here to D4D. I suggest that tag get used in the issue queue and elsewhere as well.
Also changed shortname for Mark Boulton group -- http://groups.drupal.org/drupal7ux
My proposal / idea was to work on a new design that:
a) has a particular goal to match the out of the box install profile that ships with core
b) highlights different features of the theming system - regions, different node types, etc.
c) highlights different strengths of drupal -- different data types, multi-user capabilities (profiles, blogs, additional roles)
Problems with g.d.o/usability:
- Duplicated content: "Post by topic" block in main content are and "Group categories" in sidebar are 100% same, one of them needs to go
- Outdated information: Both "Quick UI review please" and also "We are working on:" sections in usability frontpage are severely out of date
- important usability issues can now be found at http://drupal.org/community-initiatives/drupal-core/usability
Has anyone come up with a better way of presenting the list of tokens to users? I'm finding that what I'm doing is really ugly and would love to know if anyone has seen any good examples of how to present tokens in a more usable manner.
While Drupal 6 has an edit link in the primary menu, how about adding a 'home page' link and a 'create content' link in the primary/main menu by default in Drupal Core? The create content link doesn't need sub-links, it just needs to link to the node/add page.
Primary menus (especially left aligned ones directly under the site logo/name) tend to be more visible to new users than sidebar menus.
This is actually very very closely related to Redesign /admin as well as Re-work top-level admin categories. I don't want to pollute both issues with the following findings. If you are interested in reworking Drupal's administrative structure and top-level categories, you want to read on.
[01:22] * tha_sun gathered awesome usability insights from a newbie Drupal user after lengthy discussions.
[01:22] * tha_sun will incorporate that knowledge in admin menu 3.x.
[01:24] <dmitrig01> tha_sun: that being?
I haven't seen any discussion about Book usability on here yet it's one of the highlighted topics for things that need to be patched in Drupal 7 usability. Does anyone have any thoughts on how Books can be improved. I have a whole module dedicated towards Book usability improvements and while the project as a whole I'm sure implements a bit too much to be rolled into core, it does have a lot of features which make using books in Drupal faster and MUCH more user-friendly thanks to outline designer, thickbox, prepopulate and the ajax modules.Read more
Over the past two weeks at the core internationalization virtual sprint, we've been working on translatable fields. This would allow any core field attached to a node, user, taxonomy term etc. to be multilingual.
Core already allows for translating one entire node into another node, but you can't for example have translatable user profile fields, or taxonomy descriptions - and we're hoping this patch would be an enabler for that (and also make node translation more flexible).Read more
First of all I must say that Michael Haggerty's solution looks great. I've worked along the same lines with my project, that is, splitting the node form into two columns, not exercising jQuery magic. My module splits node forms into a main and right column and a footer. The admin interface makes it easy to change the region placement, weights and collapsed-state of all top-level form elements.Read more