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

WordPress Trac noreply at wordpress.org
Thu Apr 13 15:44:19 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 shireling):

 > Ah, that's another important qualifier: are we looking at this from the
 perspective of users setting up their sites (as a one-time or irregular
 task), or users customizing their site on a regular, if not daily, basis?

 I'd say both are important. To me, a new user who is likely to get
 frustrated and give up on WordPress as a whole would benefit a lot more
 from seeing all widget areas than an experienced user would suffer from
 having work through a list.

 If a user is customizing their site on a regular, if not daily, basis they
 are likely going to gain a level of familiarity with their individual
 theme and the respective widget areas/settings. They will still succeed.
 The new user who can't make widgets work and leaves will not.

 This is a different approach and would likely be more challenging but what
 if there were a toggle in the Customizer? The setting could be a choice
 between "Show all widget areas" and "Show only this page's widget areas" -
 with the former being the default on new sites.

 When set to the latter, display a note that there are other widget areas
 that aren't shown. This  way you'd have:
 - New users seeing all widgets
 - Experienced users having the ability to hide them and replicate the
 current setup if needed
 - A contextual notice to go with the setting for anyone who toggles it and
 forgets

 Perhaps add an additional contextual note on specific widget areas that
 aren't visible on the current page as well?

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


More information about the wp-trac mailing list