Add Client-Side Navigation documentation to manifest and table of contents#76351
Add Client-Side Navigation documentation to manifest and table of contents#76351juanmaguitar merged 1 commit intotrunkfrom
Conversation
|
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.
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. |
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
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.mdguide under Interactivity API Core Concepts, but the file was not registered indocs/manifest.jsonordocs/toc.json.Without these entries, the page won't appear in the documentation site's navigation or be discoverable by readers.
How?
docs/manifest.jsonfor theclient-side-navigationpage under thecore-conceptsparent.docs/toc.jsonplacing 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.