[wp-trac] [WordPress Trac] #23450: Refactor menu item meta boxes as accordion

[WordPress Trac]

#23450: Refactor menu item meta boxes as accordion
-----------------------------------------------+--------------------
 Reporter:  lessbloat                          |       Owner:
     Type:  enhancement                        |      Status:  new
 Priority:  normal                             |   Milestone:  3.6
Component:  Menus                              |     Version:  trunk
 Severity:  normal                             |  Resolution:
 Keywords:  3.6-menus needs-testing has-patch  |
-----------------------------------------------+--------------------

Comment (by chipbennett):

 As-noted in the blog post, I wanted to move discussion to Trac, as it
 seems more appropriate.

 > If you'd like to discuss this in a ticket, please create a new ticket.

 I'd prefer to comment on it in the ticket in which the change was
 introduced. I apologize if I picked the wrong ticket. I assumed it was
 this one, as a quick scan of "Menus" component trac tickets didn't reveal
 one that looked like a more likely candidate. I'll be happy to have the
 conversation in the correct ticket.

 > We've literally been discussing the revamp of menus for the 3.6 release
 for what, the ​past 2 months (with office hours twice a week)? And you
 pick now (6 days before hard freeze on feature development) to suggest
 that we start all over? :-)

 I don't spend much time in the Appearance -> Menus screen, so while I've
 been running Alpha all along, I really didn't notice this change, or
 realize its impact, until the Theme Review Queue push last week.

 > I think that the underlying difference is you are looking at it purely
 from a "power users" standpoint, and I'm looking at it from a "majority of
 our users" standpoint. Unfortunately, you can't have it both ways. The old
 menus screen was miserable for the majority of users, plain and simple.
 The steps we took in this cycle were to eliminate complexity for the
 majority of the users.

 A majority of users switch Themes frequently. Thus, a majority of users
 will have already created custom nav menus when switching Themes. Have the
 UI tests accounted for this use case? Because it appears that every single
 one of the user tests, as documented on the Make/UI site, includes:
 {{{
 Step 3: Add a menu
 }}}

 The UI is considerably more intuitive under the assumption that the user
 will add a new menu every time the UI is used. It is considerably less
 intuitive when working with ''already created'' menus.

 If that use case hasn't been tested, then yes: I think it is entirely
 valid to question whether it is ready for feature freeze.

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