[wp-trac] [WordPress Trac] #38624: Allow starter content to apply after a site has already been set up and is no longer “fresh”

[WordPress Trac]

#38624: Allow starter content to apply after a site has already been set up and is
no longer “fresh”
--------------------------+----------------------------
 Reporter:  westonruter   |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Future Release
Component:  Customize     |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+----------------------------
 Starter content for themes was introduced in #38114. In order to prevent
 the starter content from overriding a site's existing content, a
 `fresh_site` option flag was added to prevent the content from applying
 after the site has been first updated. This means the starter content has
 limited use when installing new themes to try out during the life of a
 site.

 The primary problem for applying starter content on an existing site is
 how to handle the merge conflicts, how to decide when to use the starter
 content/configs and when to use existing site content/configs. One option
 would be a button to “reset” a site to use the starter content. For more
 granularity, once the starter content is applied there could be a list of
 the settings that were modified so that you could then go through and
 evaluate each change to see if you want to keep it. Each control that has
 a setting containing dirty starter content could be highlighted in some
 way with a button that allows you to revert the starter content or toggle
 the starter content so you can compare before/after.

 This is closely related to #21666 (Customizer reset/undo/revert) and
 #31089 (Add revisions of settings to the Customizer).

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38624>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform