-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Adds frontmatter support for customizing sidebar labels independently from page H1 titles in the documentation generation process. #75068
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
base: trunk
Are you sure you want to change the base?
Conversation
…README and update manifest generation to utilize sidebar label if present
|
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. |
|
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. |
|
Size Change: 0 B Total Size: 3 MB ℹ️ View Unchanged
|
What?
Closes #60782
Adds support for customizing sidebar/table of contents labels in the documentation generation process using frontmatter, while keeping the original H1 titles on pages.
Why?
Currently, the documentation generation process extracts the H1 heading from markdown files and uses it for both the page title AND the sidebar/breadcrumb navigation.
This creates a dilemma when we want to:
As noted in #60782, simply removing words like "reference" from the H1 would negatively impact SEO and make page titles confusing. This PR provides a solution that addresses both concerns.
How?
This PR modifies docs/tool/manifest.js to:
Testing Instructions