Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pathfinding #44777

Open
mtias opened this issue Oct 7, 2022 · 2 comments
Open

Pathfinding #44777

mtias opened this issue Oct 7, 2022 · 2 comments
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.

Comments

@mtias
Copy link
Member

mtias commented Oct 7, 2022

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.

@mtias mtias added Needs Design Needs design efforts. [Feature] Full Site Editing [Type] Discussion For issues that are high-level and not yet ready to implement. [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Oct 7, 2022
@jameskoster
Copy link
Contributor

Possibly one to consider here: #45099

@jffng
Copy link
Contributor

jffng commented Jan 25, 2023

including more clearly representing what is acting as the homepage

Here's an issue to consider #45644, though the suggestion now feels a bit backwards from the approach you describe here, which "requires looking beyond the editor and into other admin views".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

4 participants