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

WordPress Trac noreply at wordpress.org
Thu Apr 13 14:27:52 UTC 2017


#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 zoonini):

 There is another use case as well:

 3. Customizer controls should always be shown, because it's inefficient to
 not have them all available when setting up a site – whether you're a new
 or experienced user.

 It's definitely not just new users who find the current implementation
 frustrating and time-consuming. It's particularly inefficient for anyone –
 new, experienced, or somewhere in between – who's setting up their site
 for the first time, or someone who just wants to add a widget to a page
 that hasn't yet had a specific template applied.

 Daniel's comment gave me an idea. What if there were a setting for
 "enterprise clients" or anyone else who wanted to ''turn off'' the ability
 to have all settings/widgets displayed in the Customizer? That would still
 provide a way for "power users" to maintain the status quo.

 > You use WordPress on a daily basis, and only want to see the controls
 you need to see because everything else is mental overhead.

 Do most people add/edit widgets and other Customizer settings on a daily
 basis?

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


More information about the wp-trac mailing list