Skip to content

View Config for the site editor v2 - #13296

Draft
oandregal wants to merge 1 commit into
WordPress:trunkfrom
oandregal:add/wp-navigation-view-config
Draft

View Config for the site editor v2#13296
oandregal wants to merge 1 commit into
WordPress:trunkfrom
oandregal:add/wp-navigation-view-config

Conversation

@oandregal

@oandregal oandregal commented Aug 27, 2026

Copy link
Copy Markdown
Member

Trac ticket: https://core.trac.wordpress.org/ticket/65981

Not to land until the site editor v2 experiment is confirmed to land. cc @youknowriad

Backports

Gutenberg PRs:

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Fable
Used for: Porting the server-side change from the Gutenberg PR. Reviewed and edited by me.

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.

…ost type.

Provides a list-type, date-descending default view for navigation menus so
the site editor's Navigation screen can read its view from the
`/wp/v2/view-config` endpoint instead of hard-coding it.

Backports WordPress/gutenberg#82138.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@oandregal oandregal changed the title View Config: Add a default view configuration for the wp_navigation p… View Config for the site editor v2 Aug 27, 2026
@github-actions

Copy link
Copy Markdown

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant