-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update: Storybook navigation updates #66177
Conversation
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. |
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @mattrwalker! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
Size Change: 0 B Total Size: 1.77 MB ℹ️ View Unchanged
|
Flaky tests detected in cebcac8. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11369645178
|
cebcac8
to
d14897a
Compare
This reverts commit d14897a.
@mattrwalker I can't spot any code changes, maybe you didn't push the relevant commits upstream? |
Big win. Nice. |
This. Something seems to be messed up with the branch. |
Should be fixed if you remove the last commit - that's necessary because it effectively reverts your changes. You can do it with:
|
Hey all, I'm closing this pull request and trying again. 🙃 You'll see separate smaller pull requests for each section/category. |
Related to #66072
What?
This pull request includes changes to update the titles and IDs of various components in their respective story files for better organization and consistency.
This PR does not address the visual design of the navigation, only the structure.
Why?
This change is part of the larger Storybook Improvements and the shared Sitemap.
How?
Organizing components in to functional groups helps categorize the content and easier to navigate and understand.
Testing Instructions
npm run storybook:dev
Screenshots or screencast