-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Description
Currently the top bar in the Site Editor displays the name of the template being edited, and this works well when you edit a template in isolation (IE via Appearance > Templates). But clicking Appearance > Editor takes you to a unique view where you might be editing template and content all at the same time.
For example: If your site is configured to display a static home page, Appearance > Editor takes you to a view where you're editing whichever template is used to display that page. This could be anything from a Theme supplied "Page" or "Index" template, to a custom template created by the user, with any name. In this view users are also able to edit the contents of that page, so displaying the template name alone in the top bar also feels like a mis-representation.
If your site is configured to display latest posts on the home page instead, then Appearance > Editor will take you to a view where you're editing either the Index or Home template (depending on what your theme supplies). But similar to the static home page scenario, it's also possible to edit the posts themselves in this view as well. So once again, the template name is not an intuitive title for this experience.
All of this is made worse by the fact that template names like "Index" are not particularly user-friendly!
Since we are removing the navigation in the Site Editor for 5.9 (#36194) we can think more critically about what to display in the top bar.
My initial supposition is that it might be better to simply display the site name, or URL in the top bar when you access the site editor via Appearance > Editor. This can also serve as a link to view the frontend, which is a feature folks have been asking for in the Site Editor for a long time:
To clarify, this would only appear when a user clicks Appearance > Editor. If you edit a template via Appearance > Template, then it still makes sense to just display the template name in the top bar.
Without wanting to get too far ahead of myself, this could potentially lay the foundation for a way to navigate around content in the Site Editor in the future as well: