-
Notifications
You must be signed in to change notification settings - Fork 206
docs(inlinealert,link,logicbutton,miller): docs migration from static site to storybook #2884
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
docs(inlinealert,link,logicbutton,miller): docs migration from static site to storybook #2884
Conversation
|
|
🚀 Deployed on https://pr-2884--spectrum-css.netlify.app |
File metricsSummaryTotal size: 4.63 MB* 🎉 No changes detected in any packages * Size determined by adding together the size of the main file for all packages in the library.* Results are not gzipped or minified. * An ASCII character in UTF-8 is 8 bits or 1 byte. |
37cda5f to
e5b9eea
Compare
e5b9eea to
f7e87fd
Compare
f870d04 to
66a0656
Compare
rise-erpelding
left a comment
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.
Hi! This was all pretty straightforward and all the stories here look good! The only comments I made here were thoughts I had on how we could organize/display the content on the docs pages a little better and a link that might help for getting those static stories into Chromatic. Happy to hear your thoughts and take another look anytime!
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.
I think Rise covered most of it! I just have one suggestion for Link, to reduce the amount of vertical space between all of the stories on its Docs page.
I also noticed that Miller columns shows an empty message for the ArgTypes doc block "Args table with interactive controls couldn't be auto-generated", because it has no controls. There doesn't appear to be a way to hide that in Storybook at the moment. There was a merged Storybook PR that closed the issue for the <Controls/> doc block, but I think another issue would need to be created with Storybook to also hide this for <ArgTypes/>. I think we can leave that for now, rather than creating a custom MDX template.

66a0656 to
93cad16
Compare
f4a7871 to
a40a449
Compare
rise-erpelding
left a comment
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.
I think this one is good to go now! Thanks, @marissahuysentruyt!
a40a449 to
0893c29
Compare
0893c29 to
2f3e58a
Compare
0fabca3 to
0128946
Compare
- moves migration notes about the previous subtle variant to the changelog - adds missing stories and documentation - adds a template for "filler text" to showcase links in context
80bd1b3 to
411c456
Compare
castastrophe
left a comment
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.
Just one last update then I think this one is ready to go
| ${when(headerText, () => | ||
| headerText.charAt(0).toUpperCase() + headerText.slice(1) | ||
| )} |
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.
| ${when(headerText, () => | |
| headerText.charAt(0).toUpperCase() + headerText.slice(1) | |
| )} | |
| ${headerText} |
Since this is a string, we don't need a when wrapper and I'm not sure we should be altering the format of the string. Thanks for making this update!
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.
Oh and a note to double check the *.test.js file too - it looks like it lost the modifiers in the header text.
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.
Oh wait- did those need that ${variant.charAt(0).toUpperCase() + variant.slice(1)} in the test file instead of the template file? Is that what you mean as modifiers?
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.
- adds headerText modifier for test cases - simplifies header text in template - adds "Neutral" to default header text arg
Description
This PR continues migrating documentation from the docs site into Storybook. The focus is on
inlinealert,link,logicbuttonandmiller. All variants of the component should now be displayed on the StorybookDocspage. Additionally, Chromatic coverage was added toinlinealert,link, andlogicbutton.inlinealert: new stories and enhanced chromatic coveragelink: new stories and added chromatic coveragelogicbutton: enhanced chromatic coveragemiller: new story descriptionsThis PR doesn't need a changeset since it's docs only.
How and where has this been tested?
Please tag yourself on the tests you've marked complete to confirm the tests have been run by someone other than the author.
Validation steps
Regression testing
Validate:
Screenshots
To-do list