Closed (won't fix)
Project:
Drupal core
Version:
7.x-dev
Component:
usability
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Sep 2008 at 00:35 UTC
Updated:
10 Sep 2008 at 13:14 UTC
Jump to comment: Most recent file
Comments
Comment #1
francewhoaThe following is a proposed dual admin interface to improve usability in Drupal 7.
With a dual interface user can easily switch from basic interface to advanced interface by clicking a button. User can return to previous interface by clicking same button 'Switch to basic interface'.
Comment #2
pasqualleyou just removed the Administration menu item from the Navigation menu.. This is really basic thing what I do on most sites..
so this needs work if you want to improve something..
Comment #3
mroswell commentedI also suspect it's a mistake to call something "easy." We don't think like new users any more. What we think is easy, probably isn't. Also, if this idea gets adopted (I'm not a fan of it) change the word "Advance" to "Advanced."
If we're worried about clutter, people should be able to select what they see and what they don't. Pre-determined "easy" is bound to be annoying. At least, that's my instinct.
Comment #4
francewhoamroswell: Good point about calling an interface 'easy'. Maybe something like 'Basic interface' would be more appropriate and would sounds better. I fixed the typo on 'Advanced'. Thanks,
Comment #5
tjholowaychuk commentedYikes.. yeah this is going nowhere fast
Comment #6
stevebayerin commentedI don't see how posting a link to this thread from 6 different g.d.o/usability threads would encourage adoption of the idea.
Comment #7
jpetso commentedCreating different interfaces for beginner and expert users means to give up on improving the expert user interface's usability by dismissing it as "too hard anyways". Also, there's no possibility for beginner users to slowly grow from n00b to expert status, because rather than following a constant learning curve, they have to do a wholesale switch after which they can't apply their previous knowledge anymore. (That's probably the main issue speaking against two-fold interfaces anywhere in the software world.)
Of course, the expert users will also have a hard time to train their users if they need to keep up with two different interfaces. And I'm not even starting on the absurd maintenance effort for core and contrib developers, each of which would need to code two interfaces than one, which is simply unfeasible. Instead of pushing one interface aside and say "this is never going to work anyways", the "advanced" interface needs to be improved until both beginners and experts can use it - and everyone in between, because there are no separate levels of knowledge, there are lots more than that. Administration knowledge is a steady line that has to be climbed, and a "dual" interface is not adequate for accommodating all these different users.
By sticking to a single interface that is actually exposed and therefore improving instead of hidden, we'll have better usability in the end, even though that's the harder way to go. Can any responsible person please dismiss this issue? Thanks.
Comment #8
Bojhan commentedSorry, Onpoc. This is really not a good idea, as jpesto mentioned it is an idea that is undo able. You should focus on hiding complexity in the current interface, rather then creating a complete new one. All the points that you mention on 1. is something we should incorporate in the interface, not split from the advanced one. Remember your not working on a very simple system, where the tasks are well defined - rather your working on a system that has lots of workflows, so there is a huge consideration to be made what are the major tasks of intermediates and what of beginners.
There is always a idea in order to fix usability, add function. However you should at all cost try to avoid this.
Comment #9
Daniel S. Jackson commentedI think something like this could be useful as a hack to solve some problems we're currently having. I would love to see it as a plugin to the current Drupal 6, but hope that Drupal 7 finds a different solution.