Skip to content

Add Client-Side Navigation documentation to manifest and table of contents#76351

Merged
juanmaguitar merged 1 commit intotrunkfrom
docs/client-side-navigation-toc
Mar 10, 2026
Merged

Add Client-Side Navigation documentation to manifest and table of contents#76351
juanmaguitar merged 1 commit intotrunkfrom
docs/client-side-navigation-toc

Conversation

@juanmaguitar
Copy link
Contributor

What?

Follow up to #75263

Add the Client-Side Navigation documentation page to the docs manifest and table of contents so it appears in the developer documentation site.

Why?

PR #75263 added the client-side-navigation.md guide under Interactivity API Core Concepts, but the file was not registered in docs/manifest.json or docs/toc.json.
Without these entries, the page won't appear in the documentation site's navigation or be discoverable by readers.

How?

  • Added an entry in docs/manifest.json for the client-side-navigation page under the core-concepts parent.
  • Added an entry in docs/toc.json placing it after "Server-side rendering" and before "Using TypeScript", matching the order in the Core Concepts README.

Testing Instructions

Once merged, the Client Side Navigation guide should be available at https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/client-side-navigation/

Note: Final documentation in the Block Editor Handbook is automatically regenerated from Gutenberg repo .md files every 15 minutes.

@github-actions
Copy link

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

  • Required label: Any label starting with [Type].
  • Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

@github-actions
Copy link

github-actions bot commented Mar 10, 2026

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: juanmaguitar <juanmaguitar@git.wordpress.org>
Co-authored-by: luisherranz <luisherranz@git.wordpress.org>

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

Copy link
Member

@luisherranz luisherranz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@juanmaguitar juanmaguitar enabled auto-merge (squash) March 10, 2026 10:50
@juanmaguitar juanmaguitar merged commit a5a6da1 into trunk Mar 10, 2026
42 of 46 checks passed
@juanmaguitar juanmaguitar deleted the docs/client-side-navigation-toc branch March 10, 2026 11:11
@github-actions github-actions bot added this to the Gutenberg 22.8 milestone Mar 10, 2026
@dsas dsas added the [Type] Developer Documentation Documentation for developers label Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Developer Documentation Documentation for developers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants