[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:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  4.7
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------

Comment (by greenshady):

 Replying to [comment:5 acosmin]:
 > @greenshady What if that content doesn't exist and the only post the
 website has is "Hello World". Wouldn't it be nicer do display some "dummy
 content" and maybe let the user know where things are and how they can
 edit said content.

 A site visitor is not a "user" and definitely not an "administrator" (by
 default, only person allowed to manage options).  Only someone with proper
 permissions should see that.

 That's why I think, if setting up a system like what's being asaked about
 here in this ticket, the customizer is the best place for it, not the
 front end of the site for the whole world to see.

 > Again, I think we are talking only about themes designed for blogs. For
 more complex themes with (recommended plugins) there isn't a way to
 showcase extra features.
 >
 > Basically, each theme released on .org is a blog theme which displays
 blog posts.

 I've seen many themes where blogging is not a focus at all.  I never
 assume we're working only with blog themes.  I've worked with 1,000s of
 themes and sites in the 10+ years I've been doing WP and blogs are often
 irrelevant.

 If we want to get rid of the requirement for accounting for WordPress'
 blogging features, that's a different topic.  I'd love to see themes be
 able to do something like `add_theme_support( 'blog' )` or something
 related to define whether they support a blog system.  But, that needs to
 be handled in a different ticket because it's unrelated to this one.

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