Make WordPress Core

Opened 9 years ago

Last modified 3 years ago

#34116 new enhancement

Rethink default install content like "Sample Page", etc.

Reported by: krogsgard's profile krogsgard Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: General Keywords: dev-feedback has-patch
Focuses: ui-copy Cc:


New installs of WordPress come built in with "Sample Page", a default blog post, and a built in comment.

I would like to propose that we rethink this content. In its current state, all it means is that any site owner needs to make some changes to their website, including either trashing or changing the sample page, editing the information in it and the sample blog post, and deleting the sample content.

IMO, there are a variety of steps I'd prefer to take, but I'll rank a few in terms of what I think have few consequences to options that may be more of a difficult sell.

  1. Change the name of Sample page to "About". Nearly every website has an about page. It's a much better option in my opinion. It's even the recommendation of the current sample page.
  2. Delete the sample comment on Hello World altogether. People get web comments, this just has to be trashed on all new installs.
  3. Change the status of "Hello World" to draft. It's not ready to publish, so let's not make it published.
  4. Change "uncategorized" to "general" or something that's not so awful. (I know this has been discussed elsewhere a good bit but I'd be sad to not mention it)

Currently the sample content is used as a defacto new user walkthrough. I would rather see proper new user onboarding, personally. But even if that's a step too far, I'd like to make some of these changes to the default content. Numbers 1 and 2 feel particularly doable to me, and 3 and 4 would be really nice additions.

Attachments (1)

34116.1.diff (2.8 KB) - added by Ipstenu 8 years ago.
New sample about page, props WCNYC 2016

Download all attachments as: .zip

Change History (17)

#1 @johnbillion
9 years ago

  • Component changed from General to Upgrade/Install
  • Keywords dev-feedback added
  • Version 4.3 deleted

See #14973 for the reason we switched away from creating a default 'About' page (tl;dr users would add an About page and it ends up with a slug of about-2).

#2 follow-up: @krogsgard
9 years ago

@johnbillion That makes me want to throw my chair :) I would love if we could make the trashed post the -2 slug in those scenarios when there is clearly a new non-trashed post that wants the slug. Surely there is still a route to my first point. Maybe we think of what we want it to be and then consider the technical needs vs dumping the idea bc it's inconvenient? Not a criticism to your valid critique... I just don't want a conversation to get squashed before it starts.

#3 in reply to: ↑ 2 @johnbillion
9 years ago

Replying to krogsgard:

I would love if we could make the trashed post the -2 slug in those scenarios when there is clearly a new non-trashed post that wants the slug.

I completely agree. #11863

#4 @scotthack
9 years ago

As part of the installation process it would be nice if I could select "No" for creating the sample page, comment, etc.

It is the first thing I delete.

#5 @ocean90
8 years ago

Related: #36702

8 years ago

New sample about page, props WCNYC 2016

#6 @Ipstenu
8 years ago

At WCNYC 2016, a few of us were chatting about this. The current 'sample page' hasn't been updated since 3.1, and the content is good but could use some modernization. While it shows two different examples (personal blog and company) it's not as clear as it could be which is which (though it should be easily inferred) and it doesn't really match the way usage of WP and the web has changed.

Per @krogsgard's suggestion, I named it 'about-page' so that if someone made a new 'about' it wouldn't cause 'about-2' but it could go either way really. My thought was that since someone might make the new page before deleting the existing one, it would still have a -2.

Props in 34116.1.diff go to @liljimmi @ipstenu @courtneydawn @camikaos @melchoyce

Last edited 8 years ago by Ipstenu (previous) (diff)

#7 @Ipstenu
8 years ago

  • Keywords has-patch added

#8 @dd32
7 years ago

Sample Theme Content has largely replaced the default content in a way, does that resolve this?

#9 @Ipstenu
7 years ago

I don't think so, since the default is still pretty outdated. If a theme has no sample content, they get this.

This ticket was mentioned in Slack in #core by ipstenu. View the logs.

5 years ago

#11 @SergeyBiryukov
5 years ago

  • Component changed from Upgrade/Install to Text Changes

Related: #47267

#12 @marybaum
5 years ago

I've had a thought that maybe we want to use those copy areas to really explain things. The copy is a little different as is on posts and pages -- we could push that into a discussion (Brief, I realize) of when you use a page versus a post.
Blocks, of course, have their own contexts.
We could carry that through to archives, custom fields and more, so that the first time anyone sees a particular content type they get an overview of what to put in it.

#14 @garrett-eclipse
4 years ago

  • Component changed from Text Changes to Themes
  • Focuses ui-copy added

#15 @poena
3 years ago

  • Component changed from Themes to General
Note: See TracTickets for help on using tickets.