[wp-trac] [WordPress Trac] #51821: Make starter content available for non-"fresh sites"

[WordPress Trac]

#51821: Make starter content available for non-"fresh sites"
-----------------------------+-----------------------------
 Reporter:  helen            |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Customize        |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 Starter content is currently restricted for use on sites that are
 considered "fresh" (see #38114 for history), typically new installs that
 haven't changed any content yet. This is a pretty limited scenario, as
 users frequently try editing the default content before heading into the
 customizer or anything else (related: #51820), and there are plenty of
 scenarios in which some content has been added but it's still early enough
 that starter content for a theme might be helpful.

 It was always intended for starter content to evolve into something more
 broadly applicable, and with the theme previewer site approaching a point
 where starter content can be used for demo purposes along with blocks and
 block patterns in the core editor, now is a good time to start figuring
 out what kind of experience existing sites should have around starter
 content, from letting the user know that starter is available to how it's
 applied (perhaps selectively) to managing or undoing those changes.

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