Twenty Seventeen: Improve user and developer experience with the customizer integration
|Reported by:||celloexpressions||Owned by:||davidakennedy|
|Component:||Bundled Theme||Keywords:||has-patch dev-feedback needs-testing ui-feedback ux-feedback|
As the default theme, Twenty Seventeen should showcase what themes can (and should) do with the customizer API. This applies to both users, via instant live previews and contextual controls, and developers, via code that follows core conventions.
Twenty Seventeen should follow all of the recommendations for themes in the official customize API documentation. Additionally, every option should be previewable with Selective Refresh and, where feasible, instant postMessage JS-based updates, as these approaches provide faster, more contextual user feedback as they make changes. Controls should be contextual to when they apply. The preview should be as accurate a representation of the front end of the site as possible. The code should be DRY and as simple as possible.
While the initial commit of the theme contains extensive work toward these goals, there are several problems with the current implementation, with #38399 discussing the front page sections handling in particular. This ticket addresses all of the major customize-related issues that don't already have complete patches elsewhere (like #38400). Because many of the issues are inter-related, they'll be addressed together initially, then we can follow up with additional adjustments as needed.