Twenty Seventeen: Merge Proposal for 4.7

https://make.wordpress.org/core/files/2016/10/panels-ui-small.mp4 https://make.wordpress.org/core/files/2016/10/colors.mp4 @matt In terms of preview experience, I agree that the full-page refresh experience and even the newer selective refresh preview mechanism are (much) slower than desirable. In the end, these are in place for backwards compatibility for WordPress’s theming system which fundamentally depends on PHP rendering. However, to quote myself on a WPSE answer I just wrote:
In closing, if WordPress themes could just be implemented with something like React we could avoid adding special support for selectively refreshing elements on the page since the changes to the state would automatically cause the desired changes in the DOM. Since we’re not there yet (although prototypes are being worked on for this) we have to settle for the next best experience for quickly refreshing parts of a page with the minimal extra effort for developers: selective refresh.
In terms of a clunky UI, it’s true that the “Customizer” UI needs iterating. Having all of the controls for manipulating changes being located in a panel and not inline with the elements being edited
Source: https://managewp.org/articles/13920/twenty-seventeen-merge-proposal-for-4-7

source https://williechiu40.wordpress.com/2016/11/30/twenty-seventeen-merge-proposal-for-4-7/