Repository navigation
Extensible Site Editor: Tracking issue #79895
Description
Overall Goal
To replace the Site Editor v1 (wp-admin/site-editor.php) with the Extensible Site Editor (admin.php?page=site-editor-v2)
Scope for This Release
Reach feature parity between the current Site Editor and the Extensible Site Editor.
Tasks
Premliminary investigations have identified the following gaps:
- Add editor plugin mounts to v2 shell #79222
- Gate v2 Site Editor styles for classic themes #79229
- [codex] Add Identity route to site editor v2 #79224
- Add welcome guide to site editor v2 #79241
- Add site editor v2 export action #79228
- [codex] Add mobile surfaces to v2 site editor routes #79227
- Fix block bindings
- Verify all screens take the view config from the endpoint that landed in 7.1.
- Home: N/A.
- Styles: N/A.
- Site editor v2: Identity takes its form from the view config endpoint #82692
- Site editor v2: navigation takes view config from endpoint #82138
- Site editor v2: pages take view config from endpoint #82140
- Site editor v2: Use the canonical template fields in the templates list #82666
- Site editor v2: templates take view config from endpoint #82456
- Site editor v2: Use the canonical wp_block fields in the patterns list #82672
- Site editor v2: patterns take view config from endpoint #82458
- Site editor v2: template parts take view config from endpoint #82457
- View Config for the site editor v2 wordpress-develop#13296 Core backports: only to land when/if the v2 experiment is merged.
- All screens take the fields and actions from the canonical places instead of using local ones. Related #74865
Open Questions & Decisions required
- Use condensed dataviews layout (and potentially implement the click to expand search as well)
- Use the right Tabs component for the different dataviews pages
- Check what extensibility we offer today in the site editor and how it can be adapted to the new site editor
- Check whether the "lazy-editor" works in all block plugins or if there's migration, opt-in strategy to do there
- Explore how to stabilize the experiment.
Activity
oandregal commentedon Jul 22, 2026
For extensibility, I'm happy to help identify gaps. We've landed a new API in 7.1 that takes the view config from a new REST endpoint (see
WP_REST_View_Config_Controllerandgutenberg_get_entity_view_config) via theuseViewConfighook. The next step is registering the fields (for dataviews and dataform) in the server (issue).Mamaduka commentedon Aug 26, 2026
It looks like Block Bindlings' bootstrap logic is missing from v2, which is then causing a Moment library warning. Calling
registerCoreBlockBindingsSourcesshould fix that, though I'm not sure what the best place for this is.Screeenshot
oandregal commentedon Aug 26, 2026
I added a new task:
Mamaduka commentedon Aug 26, 2026
A little bit of UX/UI feedback as well.
Screenshot
oandregal commentedon Aug 27, 2026
I've listed all tasks individually, so that anyone can help. Just tag yourself in the particular screen when you intend to start working on it. I've started by preparing #82138
oandregal commentedon Aug 27, 2026
I've noticed that the list layout is a bit at odds with the tabs. Perhaps does it suffice to make them scroll horizontally?
Screen.Recording.2026-08-27.at.18.24.21.mov
oandregal commentedon Sep 9, 2026
All site editor v2's screen have been migrated to use the view config from the server.
The only remaining tasks is porting the view config changes for the
wp_navigationentity that only exists in the site editor v2, so I thought we'd ship this when/if the site editor v2 becomes stable.I've also migrated some local fields to use the canonical fields we provide through the editor package. We aim to migrate all these fields to be registered in PHP at #74865
ramonjd commentedon Sep 11, 2026
Just dropping this PR as a FYI. No action required.
youknowriad commentedon Oct 14, 2026
I'm removing this issue from 7.2 and transforming it to a tracking issue. This is mostly ready but there needs to be a dedicated effort to test this with plugins and different environments before shipping it as stable. If any team or developer is willing to do that in the next weeks, please go for it.
[-]Extensible Site Editor: 7.2 Iteration Issue[/-][+]Extensible Site Editor: Tracking issue[/+]