Implement term pages and 'system pages' in WordPress #12707
Labels
Customization
Issues related to Phase 2: Customization efforts
[Type] Enhancement
A suggestion for improvement.
Milestone
WordPress has traditionally had only a simple textarea to change the description of a category or tag. For a long time Yoast SEO has had a feature that replaced this simple textarea with a TinyMCE editor instance. The reason for this is that term pages are very often of incredible SEO value.
The most obvious example of this is for webshops, where it is very hard to rank for a specific product like a bag, unless someone is searching for that specific brand of bag. What most webshops do instead is rank for the category of thing. So they rank for the word bag instead. This is then done by the
Bag
category and that lists all the bags available on the site.This has been fairly awkward to use because the user has no control over the placement of the description on the term page. So other than adding a description and hoping the theme puts it somewhere useful, there is no other way for a user to exert control over their term pages.
With Phase 2 this can be improved. The first step is to add the block editor to the the term edit screen. The second step is adding a
Posts for Term
block, that lists all the posts in the term. This combination allows the user to customize their term pages the way they want.Expanding on this, the same logic applies to what I call 'system pages'. Pages that are automatically generated with fixed content, but have to be on the site: The homepage, author pages, etc. All these pages have a fixed block:
All Posts
,Posts for Author
, etc. The homepage one allows us to drop the weird homepage setting. If the user doesn't want a post overview on their homepage they can remove theAll Posts
block. If we allow thePosts for Term
andPosts for Author
block on any page, the homepage can also be customized with these block options.@youknowriad @alexislloyd: Phase 2 leads
@omarreiss, @jono-alderson: You probably have ideas about this.
The text was updated successfully, but these errors were encountered: