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
More storybook example/docs for dynamic/multi-state buttons #4553
base: main
Are you sure you want to change the base?
Conversation
|
size-limit report 📦
|
...pshots/components/Button.test.ts-snapshots/Button-Trailing-Counter-dark-colorblind-linux.png
Outdated
Show resolved
Hide resolved
|
||
<Meta of={ButtonStories} title="Components/Button/Features/MultiStateButtons" /> | ||
|
||
# Multi-state Buttons |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See new documentation!
aca05ff
to
eb5c6c5
Compare
Co-authored-by: Lindsey Wild <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just one comment on the dependency
@@ -141,6 +141,7 @@ | |||
"@storybook/addon-links": "7.6.2", | |||
"@storybook/addon-storysource": "7.6.14", | |||
"@storybook/addon-styling": "1.3.7", | |||
"@storybook/blocks": "8.0.9", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use the v7 version of @storybook/blocks
since we're still on v7 of storybook? 👀
Fixes: https://github.com/github/accessibility/issues/6266
Changelog
New
storybook/addon-blocks
package. This allows me to provide more comprehensive documentation for a storybook example the storybook way ✨ .I've already proposed doc updates to Primer's interface guidelines. I don't think this is enough. I find additional value in having code examples with explanatory text, since the interface guidelines is more framework agnostic.
There is a need to provide additional documentation for nuanced examples alongside the code (Slack), but there isn't a standardized practice for doing that right now in storybook.
Initially I went down the route of directly adding text explanations to the storybook story, but utilizing storybook blocks and MDX feels a lot cleaner, and feels like the "storybook way". So, I am trying this storybook markdown out!
Check it out 🔍 :
📢 REVIEWERS: let me know if this approach doesn't make sense to you or if you have a different suggestion!
Are there are any concerns with adding this package? 👀
Rollout strategy
Testing & Reviewing
Merge checklist