[drupal-devel] A collection of usability problems

Bèr Kessels berdrupal at tiscali.be
Sat Sep 24 17:20:11 UTC 2005


And my concerns all boil to one thing: rushing in usability improvements 
without proper thought about it is a no-go IMO. 

We are not talking about some nodapi improvment, or wheter a cancel button 
should be a link. 
We are making decisions that form what Drupal IS. Some of the choices will 
have a great impact on what drupal can, is or serves. 
that is why I am so very reluctant about rushing such huge choices in.


On Saturday 24 September 2005 01:06, Dries Buytaert wrote:
> On 24 Sep 2005, at 00:47, Richard Archer wrote:
> > The problems identified in this thread are glaringly obvious
> > examples  poor usability and there is really no reason not to make
> > some improvements in these areas. While these improvements might
> > not result in the perfect solution, that doesn't matter. As long as
> > they make Drupal easier to use and don't break the API they are
> > worth while.
> Right on.  At this point in time, we should focus on improvements for
> 4.7, not on those for 4.8.  Everything that is meant to be for 4.8
> should be put aside.  Remember that Drupal 4.7 will be the de facto
> release for the next 6-9 months.  That is a _long_ time and thus a
> _lot_ of new users (and potential customers) that will be exposed to
> Drupal 4.7.  It is in everybody's interest to improve Drupal 4.7's
> usability in the few weeks that we've left.
> --
> Dries Buytaert  ::  http://www.buytaert.net/

More information about the drupal-devel mailing list