Posted by berenddeboer on June 27, 2009 at 9:06am
8 followers
| Project: | Drupal core |
| Version: | 7.x-dev |
| Component: | user interface text |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
| Issue tags: | d7uxsprint, ui-text, Usability |
Issue Summary
Starting to work on UX-Sprint 2009 issue: http://sprint.drupalusability.org/content/global-menu-settings-are-confu...
Comments
#1
#2
The description for the advanced option is very confusing, and hard to explain. It is theme dependent as well. This feature should be removed from Drupal and themes who support a "submenu" should pull out the child links themselves, not really on this confusing ability.
#3
Patch from UX Sprint 2009 where we tried to improve the descriptions.
#4
The terms "Main links" and "Secondary links" are very confusing. Especially as you definitely will mix it up with the terms "Main menu" and "Secondary menu" that stand for something different. We should think about a different naming. We left it for now.
The user has to immediately understand what those terms mean and where these menus appear on a page. A small descriptive graphic might help.
#5
Screenshot for the changes that are in the patch
#6
#7
I thought Berend advocated that the advanced option was to be removed?
Reading the text on the screenshot, I'd say it is still very confusing. ;-)
#8
The last submitted patch failed testing.
#9
fixing tag
#10
Dries: Well, we opt for the Advanced option to be removed. But since this is a different patch (themes should pull out the secondary level from primary or secondary links themselves). But since this patch is not there (I think we have to create an issue for this) we left it in for now.
But maybe we should just throw it out - It could be enough if it is explained in the documentation somewhere.
#11
We are planning to shoot this page dead.
"Default menu for new content" moved under content type editing in #351249: Finer control over the Parent Menu select box and "Source for the x" should go away in #503810: Convert primary and secondary menus to blocks
#12
See the other issue.
#13
@kika - you beat me to it in #11. By converting menus into blocks and adding finer control over the parent menu select box the global menu settings page can be dropped completely. This would be a huge win.
#14
Can this issue be closed? admin/structure/menu and admin/structure/blocks are looking great.