Make WordPress Core

Opened 3 years ago

Last modified 8 months ago

#38892 new feature request

Twenty Seventeen: A "Page Content" Section Option would be nice

Reported by: johnjamesjacoby Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Themes Keywords: 2nd-opinion reporter-feedback
Focuses: Cc:
PR Number:


Sorry if this has already been talked about, but in testing out Twenty Seventeen, there's 1 thing that I wish I could do with the Front Page theme options sections.

For my use-case, the WordPress page gets used as a placeholder for the root/front of the website, and is either empty or not the predominant content for that page. I'd like a way to deemphasize it, remove it entirely, or have "Page Content" (or something) as a Section instead.

And if the_content or post_title for the home page are empty, I think that section doesn't end up looking right. I also think it's /fairly/ common amongst the heavier WordPress themes to not force the home-page content into the output of the home-page anywhere, so I'm creating this ticket in case I'm not alone in missing this experience.

Sorry again if this is a duplicate. I had a hard time searching around since any combination of 'front page theme option customizer sections' return Brazilian's of results.

Change History (4)

#1 @davidakennedy
3 years ago

@johnjamesjacoby Thanks for the ticket! I don't think this was brought up before, so no worries there.

What would be a use case for this? Leaving that content blank? I don't think I've ever set a static page as the home page and not wanted to show its content.

I could see the need of maybe wanting to make this fail more gracefully, because it doesn't look good if you have no content in there. But that seems like it would be a rare use case for this theme in particular. Plus, now it can be hidden with custom CSS in Core. :)

#2 @davidakennedy
3 years ago

  • Keywords reporter-feedback added

This ticket was mentioned in Slack in #core-themes by davidakennedy. View the logs.

3 years ago

#4 @davidakennedy
3 years ago

  • Milestone changed from Awaiting Review to Future Release

It makes sense to improve things here, but it's not critical for 4.7.

Note: See TracTickets for help on using tickets.