usability

I've been doing some work on the node administer form at admin/content/node, to move the filter storage from a session to $_GET params in the URL. This could have several benefits:

1. The filtered pages are then bookmark-able and shareable
2. The filters will be reset every time a user navigates away for an extended period of time, or through multiple pages

There are also disadvantages:

<

ol>

Hi. This summer I wrote Drupal's Plugin Manager module. It is designed to allow users to install modules and themes directly from drupal.org using local ftp or ssh. Now, after a few releases and with another person on the project (jabapyth,) I'm starting to notice the traps that we've carefully laid out for ourselves. Thus, Jabapyth and I are planning to rewrite the UI for the module. This is where I was hoping for some help. I hope for us to create an interface that is not a headache waiting to happen.

I've been working on a port of the Outline Designer module to Drupal 6 and it's almost ready for release. I've got a demo up of the current progress / direction that the project is taking but it's drastically changed since the Drupal 5 version; both architecturally and in terms of usability. It now piggy-backs functionality of the Ajax, Book, and Thickbox modules. You can check out the demo / screencast below. Feedback is muuuuuch appriciated as this module is still geared towards making Drupal more usable for the education crowd.

on the current homepage (http://drupal.markboultondesign.com/iteration8/homepage_notloggedin.html) there is a section called 'Develop with Drupal'. This section is targeted at 'outsiders' (those not v familiar with Drupal) who are developers. These people will be evaluating Drupal from more of a technical perspective so we want to point some signposts in here that will take them to content that will impress them and make them excited about the opportunity and potential of using Drupal.

Here are the links that are currently included in this section:

Modules and Themes

I would like to open a discussion after a chat on #drupal-usability channel about admin/build/themes and administration theme settings page.

Based on the fact that multiple theme functionality will be removed from D7 core and moved to contrib.

Here is the first draft we can start with: http://www.flickr.com/photos/30032901@N04/2922043198/sizes/o/

Three tabs
- List - list of installed themes where user can choose front-end and back-end themes

This is my first proposal for changes to the content creation form.

They are minor but yet I feel they will make things easier. I thought let's get a few basic things rolling before we get to the really hard stuff later on. Pease do comment on each of the four changes seperatly.

So here are my thoughts behind this mockup.

<

ol>

The email notification links for a closed discussion should not contain the link for the Post Reply since none can be added. This is confusing to any user but particularly someone new. Maybe the text should read "Post reply: Closed discussion".

OK, so I've spent a bit of time rethinking the update status page... I think it's time for some feed back.

I've broken it into 4 areas: Critical Updates, Available Updates, New Versions, and Up To Date.

Critical Updates are those which need updating right now.
Available Updates are those for which an update exists but is not mandatory.
New Versions would be like an upgrade from imagecache to imagecache 2.
And Up To Date is obvious.

I don't have core showing on here, but it would appear in the category that applies to it (only ever Critical, New Version or Up To Date).

DRAIP: Drupal Remote Administration Interface Protocol

"Pay no attention to that man behind the curtain, err drape, err draip!"
--- with appologies to L. Frank Baum :)

Update: This effort is now combined with the User Interface best practices wiki.