Admin bar: Always show the site editor link when using a block theme

[ptesei]

Trac ticket: core 62368

Summary

Edit site, Ambiguity and inconsistency of the admin bar link to the site editor:
Have you ever accidentally clicked on "edit site" instead of "edit page"?
I've been working extensively with block themes lately, and I find myself making this mistake often, even though I clearly know the difference between the two buttons. After asking around, it seems I'm not the only one.

Secondly, when I'm in the admin area working on a block theme, I always look for the "Edit site" button, but it's not there. Instead, I have to navigate to Appearance > Editor.

Here's my simple proposition:

The link is always called "Editor"
The link is always visible if you have activated a block theme.
It's a small change, but it would greatly improve the user experience!

Changers

• Renamed 'Edit site' to 'Editor'
• Provide a shortcut link to the editor in the admin

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props mosne.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.