[wp-trac] [WordPress Trac] #38114: Make it easier to visualize where to put your content in a given theme (aka "dummy content")

[WordPress Trac]

#38114: Make it easier to visualize where to put your content in a given theme (aka
"dummy content")
----------------------------+-----------------------
 Reporter:  helen           |       Owner:  helen
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  4.7
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+-----------------------

Comment (by westonruter):

 Replying to [comment:25 helen]:
 > I'm imagining no UI (in core) - themes choose from a selection (which
 can be extended, but I would think that for .org themes they should be
 discouraged from doing so) that best showcases that theme. This perhaps
 disadvantages "do it all" themes, but I don't think that's a bad thing. :)

 So you're thinking that themes would fetch the dummy/initial content from
 WordPress.org rather than bundling the dummy/initial content inside the
 themes themselves? Or should both be possible?

 > So - possibly/probably, but later. Because I'm not thinking of much/any
 UI for this in core, I'm not sure it would be wise to allow that right
 away, as you'd likely want to prompt a user in a "this theme works best
 with a static front page, try it out?" sort of fashion. It is a huge
 hiccup in the theme set up process though, so if it seems like a
 reasonable thing to tackle once we have a basic swing in place, I'm up for
 it. See #19627.

 I guess I'm having a hard time understanding the scope of what
 dummy/initial content is suppose to include. Is it just theme mods and any
 associated sideloaded images? Or is it also options, posts/pages, widgets,
 and nav menus? If only the former, then there's not the concern about
 overriding existing data: the injection of the dummy/initial content could
 be skipped if the theme mods not empty (meaning it was activated before).
 But to me it seems that limiting the initial/dummy content would be quite
 limiting in terms of providing users with a fully-configured initial site
 setup that they can then extend?

 So if a theme does work best with a static front page and this static
 front page is also designed to have 3 widget areas, then I should think
 that when previewing this theme, these should be all configured and ready
 to go live if the user hits Save & Activate.

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