[wp-trac] [WordPress Trac] #26899: Theme Activation Workflow with Customizer

[WordPress Trac]

#26899: Theme Activation Workflow with Customizer
-----------------------------------+------------------
 Reporter:  chipbennett            |       Owner:
     Type:  enhancement            |      Status:  new
 Priority:  normal                 |   Milestone:  4.1
Component:  Themes                 |     Version:  3.4
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch ux-feedback  |     Focuses:  ui
-----------------------------------+------------------
Changes (by celloexpressions):

 * keywords:  ui-feedback needs-patch => has-patch ux-feedback
 * component:  Customize => Themes
 * milestone:  Awaiting Review => 4.1


Comment:

 Trac-ing https://irclogs.wordpress.org/chanlog.php?channel=wordpress-
 dev&day=2014-10-14&sort=asc#m940085. From @johnbillion:
 > We should make the 'Live Preview' button the default when browsing
 themes, instead of 'Activate'. The customiser is killer now.
 > Or scrap the Activate button entirely and make people go through the
 customiser

 Let's turn this ticket's proposal around: it really doesn't make sense to
 activate a theme ''without'' live-previewing/customizing it first for most
 users. Therefore, we should guide the user in the best/most common path to
 activating a theme:
 1. Select potential theme from `themes.php`
 2. Live Preview/Customize, including setting up widgets & menus and
 editing theme options
 3. Activate theme, which you've already customized and already know
 exactly how it looks/works on your site

 All we need to do to achieve this, without running into complaints about
 removing the activate button for power users, is to make "Live Preview"
 the primary action and "Activate" secondary. We could also switch the
 order, although I definitely prefer the primary button on the right. The
 primary button implies the best option to try, and it makes sense to
 preview a theme before activating it live on the site. Once users click
 "Live Preview", the preview, configure & activate workflow is clear, so I
 think nudging users into this flow is enough.

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