[drupal-devel] Re: Remove admin.module

Carl McDade carl_mcdade at yahoo.com
Wed Jan 26 01:01:05 UTC 2005

Bèr Kessels wrote:
> Op dinsdag 25 januari 2005 22:49, schreef Todd Grimason:
>>Perhaps a suitable solution could be setting a CSS id attribute
>>('is_admin'?) to be used in the HTML body tag so that those who want
>>to could format admin pages differently? Or some other sort of CSS
> You can use sections.module perfectly for this.
> Regards,
>  Bèr

But has anyone noticed that There is a growing problem with the user not 
being able to find functionality within the present UI because most of 
it is hidden within collapsed list. At present listing is starting to 
get more out of hand as modules and their administration become more 
complicated. This will be escalated by the addition of more core modules 
which are not configurable and cannot be turned off in most cases. A UI 
  I nested list should never be more than 3 deep and 7 items per list. 
after that the user starts getting lost and frustrated. I is very close 
to CLI in that the user is expected to learn the structure and syntax 
first before being able to give a command. The list admin structure is 
counter intuitive and has absolutly no visual cues. Visual overview, 
grouping and visual cues are the reason for the popularity of just about 
  every UI including the most popular, Windows.

In this particular case it is not a matter of themeing either. The child 
pages are complete and have explainations within them. It it the UI 
leading to them that is the bottleneck. There is no overview of the 
structure of the admin UI.

More information about the drupal-devel mailing list