-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Widgets editor: Add basic options for extensibility #25758
Conversation
- Adds a WidgetAreas.Sidebar Fill component so that third party plugins can add custom UI to the widget editor's sidebar. - Sets the widget editor's block editor provider to not use a sub-registry, so that third party plugins can add custom blocks (including custom UI) to the block editor used in this screen.
Size Change: -557 B (0%) Total Size: 1.18 MB
ℹ️ View Unchanged
|
We will need to document this for it to be useful. I've created #25759 to track all of the technical documentation that needs to be written for this screen ahead of 5.6. |
Do we have a clear idea of what kind of use-cases these slots will serve? In the PostEditor we've took the approach of generally avoiding extensibility APIs unless the use-case is clear enough and the API semantic enough. A slot to add something to a sidebar is "position based" and not semantic for me. |
A good example that comes to mind is Jetpack's visibility settings — I believe they exist per widget, so it would be more about extending each block wrapper when used in the context of the widget-editor. |
@ryanwelcher: Did you have anything concrete in mind when opening #18068? |
I removed the This PR now just makes it so that you can customise the widgets editor using typical |
Just noting this requires more work as noted in #15644 |
Closes #18068.
Adds some really basic options for extending the widgets editor.
Adds aWidgetAreas.Sidebar
Fill
component so that third party plugins can add custom UI to the widget editor's sidebar.Sets the widget editor's
BlockEditorProvider
to not use a sub-registry, so that third party plugins can add custom blocks (including custom UI) to the block editor used in this screen.How to test
Paste this into your DevTools console:
Expand