[wp-trac] [WordPress Trac] #37661: A New Experience for Discovering, Installing, and Previewing Themes in the Customizer

[WordPress Trac]

#37661: A New Experience for Discovering, Installing, and Previewing Themes in the
Customizer
-------------------------------------+-------------------------------------
 Reporter:  celloexpressions         |       Owner:  westonruter
     Type:  feature request          |      Status:  reopened
 Priority:  high                     |   Milestone:  4.8
Component:  Customize                |     Version:  4.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-           |     Focuses:  ui, accessibility,
  screenshots needs-testing has-     |  javascript
  user-testing has-ux-feedback       |
-------------------------------------+-------------------------------------
Changes (by celloexpressions):

 * milestone:  Future Release => 4.8


Comment:

 Proposed next steps:
 1. Revert [39153] (so that revert will be clean), then revert [39140],
 closing this ticket and #34843 as fixed.
 2. Reopen #38365 and #38663 and commit the previously-supplied patches for
 both.
 3. Reopen #38626 and work on/commit a patch. Also try to find where the
 documentation was incorrect and fix it.
 4. Patch and commit #38666.
 5. Open a new ticket to specifically improve the theme browsing experience
 in the customizer. The customizer was intended to reuse the admin
 experience and have that part be out of scope for this ticket, but ended
 up changing and ultimately being the primary reason that this was deemed
 unready to ship. With the base functionality and the related pieces in
 trunk, and the bugs fixed, this aspect will be much easier to iterate on
 and re-polish well within the 4.8 timeline.

 These steps can begin as soon as 4.7 is branched, and we should be ready
 to focus on step 5 within a week or two.

 @folletto has already started working on additional proposals for
 improving the theme browsing experience and is consulting with other
 design team members as well. From a workflow perspective, though, we can't
 hinge this entire project on that piece, especially with several months of
 trunk being open to iterate directly. Having something in trunk
 facilitates the feedback that this project has sorely lacked and also
 avoids maintaining an untenable patch and interfering with other pending
 changes throughout the component. Alternative UX approaches will be much
 easier to design, develop, test, and iterate on this way. There is good
 precedent for iterating in trunk from #27055, the initial theme install
 experience redesign for the admin in 3.9.

 A technical aside, in response to the suggestion above to query .org
 directly from JS, see [28126]. We should probably maintain the current
 approach of going through WP to get to the .org API for those reasons.

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