[wp-trac] [WordPress Trac] #32678: Audit toolbar links and content

WordPress Trac noreply at wordpress.org
Fri Jul 3 17:10:42 UTC 2015

#32678: Audit toolbar links and content
 Reporter:  helen                              |       Owner:  helen
     Type:  task (blessed)                     |      Status:  assigned
 Priority:  normal                             |   Milestone:  4.3
Component:  Toolbar                            |     Version:
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch make-flow needs-testing  |     Focuses:  ui

Comment (by ryan):

 Replying to [comment:73 helen]:
 > I need to know what the path of least resistance is for 4.3, whatever is
 happening with this patch is nowhere near ready. All I care about for this
 release is not mixing up links into different contexts. My take is that a
 separate Customize menu, with or without a submenu, on both front and
 back, is enough for now. All other links in both toolbar AND admin menu
 should go to admin screens, with the exception of the customize link under
 appearance. This means deciding on an icon - let's please steer clear of
 anything remotely implying layout. I would rather a brush than anything
 along those lines.

 Aye. I'll talk this through to make sure I'm on the right page. Putting
 Customize at top-level in the toolbar is the easiest and most direct way
 to avoid mixing contexts. To avoid all context mixing, we need Customize
 to be accessible from both front-end and back-end toolbars. Customize
 can't be in a submenu of Dashboard because Dashboard is only on the front-
 end toolbar and because having Customize and Appearance in the same menu
 is context mixing. So, top-level toolbar it goes.

 That means adding another top-level without taking any other top-levels
 away -- as i9b does with Comments. This visual record shows production
 menus on an iPhone 6+ for both a single site and multisite install.


 Here's single site on the smaller Nexus 5.


 It'll be a bit cluttered with an extra top-level, but we can live with it
 for a release. And, I'm pretty sure we'll end up with Customize remaining
 top-level, so this addition is in the direction we're headed.

Ticket URL: <https://core.trac.wordpress.org/ticket/32678#comment:76>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list