Add command to navigate to site editor

[benazeer-ben]

What?

Enhancement for the scenario mentioned in #61460

Why?

Currently there is no command option to go back to site editor from edit post or page views.

How?

Added command to navigate to Site Editor.

Testing Instructions

• Open the WordPress Editor
• Go to Posts or Pages in the WordPress admin.
• Open a new or existing post/page to enter the block editor.
• Open the Command Palette
• Access the Command Palette by pressing Cmd + K on Mac or Ctrl + K on Windows, or via the menu if available.
• In the Command Palette, look for a command labeled something like "Go to Site Editor".
• Ensure that this command is listed among the available commands.
• Execute the Command
• Select the Go to Site Editor command from the Command Palette.
• Confirm that executing the command redirects you to the Site Editor interface.

Screenshots or screencast

go-to-site-editor.mp4

[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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: benazeer-ben <benazeer@git.wordpress.org>
Co-authored-by: richtabor <richtabor@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: annezazu <annezazu@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>

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

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @benazeer-ben! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[annezazu]

This works!

testing.command.mov

With that said, I wonder about the naming. Can we go with "Open the Site Editor" as that aligns with some of the "open" language outlined here #50407 ? I also am curious about the icon used and wonder if it should be something else:

@WordPress/gutenberg-design for any quick thoughts on the icon!

[richtabor]

The command should also not be available when you're already in the Site Editor:

@WordPress/gutenberg-design for any quick thoughts on the icon!

Let's just not use an icon, all commands don't need one.

[t-hamano]

Thanks for the PR!

One thing to note here is that classic themes don't have access to the site editor root, so we can't add this command in classic themes.

Here's an example of code to detect if it's a block theme:

gutenberg/packages/edit-site/src/components/add-new-pattern/index.js

Lines 51 to 53 in 7ff7679

	const { getCurrentTheme, getPostType, canUser } = select( coreStore );
	return {
	isBlockBasedTheme: getCurrentTheme()?.is_block_theme,

We could add a similar code to the existing useSelect hook.

[jameskoster]

Do we refer to the "Site Editor" anywhere else in the UI? I recognise it's a familiar term to wp community members, but otherwise we're introducing another name for the same thing. The wp-admin navigation refers to this section simply as "Editor" (under "Appearance"). The root panel is titled "Design".

The command should also not be available when you're already in the Site Editor:

I think the purpose is to go from the full screen editor (in either post or site editor) to the site editor root? This also suggests to me that the naming isn't quite right... "Site editor" means different things to different people.

[jasmussen]

I'm still slightly partial to Site view and Edit view, though I recognize they haven't really caught on:

Your point is valid enough. Another way to frame it, however, is: do we support aliases? If someone searches for "site editor" as a command, even if we chose not to surface the specific name in the palette, it would still be useful for fuzzy searching. We support aliases for blocks already, which is why all of these results show up in a search for "image":

[t-hamano]

The term "Site Editor" is used in the following places, but I'm not sure if this term is official.

Site Editor Mobile Layout > Site Hub Tooltip Label

Site Editor > Page Screen > Welcome Guide

Site Editor > Welcome Guide Area Label

[t-hamano]

@benazeer-ben Thanks for the update!

As mentioned in the comment, this command cannot be exposed to classic themes. Could you update this PR?

One more thing I noticed is that the site editor is not accessible to all users. As implemented here, the command should only be exposed if the user can create templates and it is a block theme.

[benazeer-ben]

Thanks for that suggestion @t-hamano

Now the PR is updated with both the conditions.

[t-hamano]

From a code perspective, I think it's ready to ship, but should the phrase "Open Site Editor" be allowed? I don't think the Command Palette currently lets us set alias labels.