Pathfinding #44777
Labels
[Feature] Site Editor
Related to the overarching Site Editor (formerly "full site editing")
Needs Design
Needs design efforts.
[Type] Discussion
For issues that are high-level and not yet ready to implement.
This is an umbrella issue for improving the access points to various editing contexts.
WordPress has generally maintained a clear split between content and templates. Historically, templates were outside the reach of regular users so most of its usability problems were confined to where template and content clashes the most — notably the "homepage" which exists in several possible states in WordPress as a template (home, front-page), setting (static home page), and content (when using static homepage).
This also meant that representing pages like "blog", "archives", or "search" wasn't viable in the interface because nothing was actually editable, instead existing as indirect settings in places like Settings > Reading or the permalink structure. Even though templates representing dynamic pages occupy a concrete path in the site structure they were not visible as such when a user navigated their pages or built navigation menus.
The introduction of the site editor and block themes is a significant opportunity to address some of these shortcomings at a more fundamental level, but it requires looking beyond the editor and into other admin views (like the list of pages and post types) to help connect the dots. For example, we could explore showing the "Blog" as a dynamic page with "Archive", "Date", "Categories", "Tags" as virtual subpages linking to the contextual template editing place in the site editor. This would allow reaching the right template without having to go first through the editor entry point, including more clearly representing what is acting as the homepage. The sidebar inspector for the template ought to also include settings present in Reading (like number of posts, etc).
Related to this, there are a few issues logged to explore surfacing template editing attached to individual pages or posts.
The text was updated successfully, but these errors were encountered: