Context Navigation

Changes between Initial Version and Version 1 of Ticket #32678, comment 76

initial	v1
4	4	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.
5	5
6		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.
	6	That means adding another top-level without taking any other top-levels away (i9b removes Comments to make some room for Customize). This visual record shows production menus on an iPhone 6+ for both a single site and multisite install.
7	7
8	8	https://make.wordpress.org/flow/2015/06/29/toolbar-survey-iphone-6/