[wp-trac] [WordPress Trac] #40432: Customizer: Should we stop contextually hiding features?

[WordPress Trac]

#40432: Customizer: Should we stop contextually hiding features?
-------------------------+------------------------------
 Reporter:  melchoyce    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by michelleweber):

 I heartily +1 all of this. I'd suggest some language tweaks to try and
 keep things less formal/friendlier, like:

 ''“To edit this widget, visit the page that displays it. (Yes, you can
 move around your site while the Customizer is open!)”''

 (For many of the new folks I work with, it doesn't occur to them that they
 can click around on their sites while the customizing panel is open, which
 contributes to the confusion.)

 > I'd encourage us '''not''' to change the widget order in the Customizer
 depending on the view. Doing that places an unnecessary extra cognitive
 burden on users.
 >
 > Instead, I would suggest:
 >
 > - Keeping the order of widget areas the same on every view (i.e.
 '''not''' pulling out unpreviewed areas and displaying them separately at
 the bottom)
 > - Perhaps displaying the names of un-previewed widget areas in a
 different way, such as italicized text
 > - Including a note at the top of each individual undisplayed widget area
 (after you open it), like: "“To view this widget area in the preview area,
 navigate to a view that displays it”"

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40432#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform