[wp-trac] [WordPress Trac] #23716: Discuss theme locations as meta box vs. checkboxes

[WordPress Trac]

#23716: Discuss theme locations as meta box vs. checkboxes
--------------------------+------------------------------
 Reporter:  lessbloat     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Menus         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  3.6-menus     |
--------------------------+------------------------------
Changes (by DrewAPicture):

 * keywords:   => 3.6-menus


Old description:

> Relocating a side topic discussion that started on the
> [http://make.wordpress.org/ui/2013/03/07/heres-the-last-round-of-menus-
> usability-tests/#comment-22673 make/ui P2], and then moved to the
> [http://core.trac.wordpress.org/ticket/23450#comment:16 wrong ticket].
>
> To summarize chips last post (and kick us off here), here are the
> concerns Chip would like to address:
>
> 1) When assigning pre-defined custom menus to a Theme's defined Theme
> Locations, the process now requires considerably more steps, clicks, page
> refreshes, and time
>
> 2) When looking at the "Select a menu" dropdown, there is no way to
> determine if all Theme locations have an associated custom menu assigned
>
> 3) When editing a given menu, in the Theme Location field checkboxes,
> there is no indication that a given Theme Location already has a custom
> menu assigned to it
>
> 4) With long-ish custom menus, the "Theme Locations" field is buried
> "beneath the fold", resulting in no initially visible UI for assigning
> the current menu to a Theme Location
>
> 5) Overall, the page now seems to emphasize adding/editing custom menus,
> and seems to deemphasize assigning custom menus to Theme Locations, and
> the latter is arguably the more important role/task for Appearance ->
> Menus

New description:

 Relocating a side topic discussion that started on the
 [http://make.wordpress.org/ui/2013/03/07/heres-the-last-round-of-menus-
 usability-tests/#comment-22673 make/ui P2], and then moved to the
 [http://core.trac.wordpress.org/ticket/23450#comment:16 wrong ticket].

 To summarize chips last post (and kick us off here), here are the concerns
 Chip would like to address:

 1) When assigning pre-defined custom menus to a Theme's defined Theme
 Locations, the process now requires considerably more steps, clicks, page
 refreshes, and time

 2) When looking at the "Select a menu" dropdown, there is no way to
 determine if all Theme locations have an associated custom menu assigned

 3) When editing a given menu, in the Theme Location field checkboxes,
 there is no indication that a given Theme Location already has a custom
 menu assigned to it

 4) With long-ish custom menus, the "Theme Locations" field is buried
 "beneath the fold", resulting in no initially visible UI for assigning the
 current menu to a Theme Location

 5) Overall, the page now seems to emphasize adding/editing custom menus,
 and seems to deemphasize assigning custom menus to Theme Locations, and
 the latter is arguably the more important role/task for Appearance ->
 Menus

 3.6-Menus Tracking Ticket: #23607

--

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23716#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software