[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:  4.0
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui
-------------------------+------------------------------

Comment (by JoshuaWold):

 We discussed this ticket today on Making WordPress #design Slack channel:
 https://wordpress.slack.com/archives/C02S78ZAL/p1499962031146714

 = '''Agenda''' =
 * Decide on next steps for this ticket and how we can move it forward

 = '''Notes''' =
 * In order to really figure out the best way forward we need a clickable
 prototype.
 * We had some discussion about the overall benefits/negatives of this
 ticket, and ultimately settled on testing it out to validate.
 * The eyeball symbol could cause some visual clutter, but it’s the best
 icon we can think of for now, especially since there is precedent for it
 in WordPress admin
 * Eventually when this is built we’ll have some media folks test it and
 see if it works for them (@jeffpaul we might have some folks we could also
 run this by)
 * Once the prototype is complete Tammie will create a Make blog post and
 encourage feedback

 = '''Next Actions''' =
 * Create a higher fidelity clickable prototype with based on Options 4 and
 5
 (https://core.trac.wordpress.org/attachment/ticket/40432/Widget%20Options%20v2.png).
 * Add at least a dozen widget areas in the Customizer panel for the sake
 of the prototype
 * Show a fake preview with the visible widgets displayed in the Preview
 area

 cc @westonruter, @melchoyce

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