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

Consider removing "Settings" and "Styles" from the Site Editor More Menu #51861

Closed
richtabor opened this issue Jun 23, 2023 · 4 comments
Closed
Assignees
Labels
[Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") Needs Design Feedback Needs general design feedback. [Status] In Progress Tracking issues with work in progress [Type] Task Issues or PRs that have been broken down into an individual action to take

Comments

@richtabor
Copy link
Member

Was resolving #51859 when I noticed an inconsistency between the post and site editors. There is not a Plugins > Settings control within the post editor menu; so do we need one in the Site Editor? If not, do we need the "Styles" control as well?

Both the Styles and Settings sidebars can be invoked from the editor header; seems a bit redundant to have these controls in both places.

CleanShot 2023-06-23 at 12 21 50
@richtabor richtabor added Needs Design Feedback Needs general design feedback. [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Jun 23, 2023
@richtabor richtabor changed the title Consider removing "Plugins" section in the Site Editor More Menu Consider removing "Settings" and "Styles" from the Site Editor More Menu Jun 23, 2023
@jasmussen
Copy link
Contributor

Great question, there's some arcane lore context to this one so let me dive in.

The answer is, there is a plugins menu in the post editor, but only for sidebar plugins. Shown here, the Jetpack plugin:

plugins

The menu item exists because you can un-pin the sidebar plugin, but still get it back. In principle it should exist and behave the same in the site editor, i.e. it should exist when you have a sidebar plugin installed, such as CBT.

However your issue surfaces a couple of inconsistencies. For one, CBT can't be unpinned. To me that suggests the pinning feature is optional, it shouldn't be optional, and every sidebar plugins should have a star here in the header:

Screenshot 2023-06-26 at 09 10 44 Screenshot 2023-06-26 at 09 10 50

Secondly, it seems the plugins section exists even when you don't have any plugins installed. That doesn't seem useful. I wonder if it's because global styles is considered a sidebar?

@richtabor
Copy link
Member Author

I wonder if it's because global styles is considered a sidebar?

I think that's it exactly. And you shouldn't be able to unpin it anyhow.

For one, CBT can't be unpinned.

CBT should emulate the unpin/pin functionality.

In short, Plugins should only be available if there are indeed plugins (like CBT) plugging into the UI. Settings and Styles are core features, not plugins that should be unpinnable.

@jasmussen
Copy link
Contributor

CBT should emulate the unpin/pin functionality.

Just to clarify, I think we need for this functionality to not be optional for plugins, so it should exist on the core side.

In short, Plugins should only be available if there are indeed plugins (like CBT) plugging into the UI. Settings and Styles are core features, not plugins that should be unpinnable.

Right: any plugin that registers a plugin sidebar should be unpinnable and re-pinnable through an entry in the plugins menu, and it should happen automatically.

@jordesign jordesign added the [Type] Task Issues or PRs that have been broken down into an individual action to take label Jul 18, 2023
@github-actions github-actions bot added the [Status] In Progress Tracking issues with work in progress label Oct 24, 2024
@youknowriad
Copy link
Contributor

Given the discussion here and the linked PR. It seems we want to keep the "styles" menu in the site editor, so I'm closing this issue.

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 Feedback Needs general design feedback. [Status] In Progress Tracking issues with work in progress [Type] Task Issues or PRs that have been broken down into an individual action to take
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants