-
Notifications
You must be signed in to change notification settings - Fork 195
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(progressbar,meter): migrate docs from static site to storybook #3186
docs(progressbar,meter): migrate docs from static site to storybook #3186
Conversation
|
🚀 Deployed on https://pr-3186--spectrum-css.netlify.app |
File metricsSummaryTotal size: 4.31 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. |
0691c04
to
2de2250
Compare
2de2250
to
dc23de4
Compare
dc23de4
to
e2796d5
Compare
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.
A few updates requested to the testing suite - looks great!
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.
Leaving a few small comments!
}, | ||
}; | ||
|
||
/** | ||
* By default, progress bars are determinate and have a blue fill that shows the progress. This component should have a label at the start of the track that gives context about the operation being performed. In rare cases where context is sufficient and an accessibility expert has reviewed the design, the label could be undefined. These progress bars should still include an “aria-label” or “aria-labelledby” in HTML, depending on the context. The label is always placed above the track. |
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.
Some of this gets repeated in the "Without label" story, do you think it needs to be in both places?
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.
mmmm probably not. I feel like this is the teacher in me, wanted to reiterate an important point about not using the value label without the label 😆
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.
There's still a bit of repetition around L147:
but in rare cases where context is sufficient and an accessibility expert has reviewed the design, the label could be undefined.
f383888
to
b63e601
Compare
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.
Calling out a bit of repetition that's still on the progress bar Docs page, but otherwise good to go!
}, | ||
}; | ||
|
||
/** | ||
* By default, progress bars are determinate and have a blue fill that shows the progress. This component should have a label at the start of the track that gives context about the operation being performed. In rare cases where context is sufficient and an accessibility expert has reviewed the design, the label could be undefined. These progress bars should still include an “aria-label” or “aria-labelledby” in HTML, depending on the context. The label is always placed above the track. |
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.
There's still a bit of repetition around L147:
but in rare cases where context is sufficient and an accessibility expert has reviewed the design, the label could be undefined.
b63e601
to
0bf91c5
Compare
@rise-erpelding Should be taken care of now! 0bf91c5 |
- adds relevant S2 controls to template - expands test coverage to include without label and without value label - adds stories and documentation to docs page - adds additional migration guide context to CHANGELOG
- expands test coverage to include without label and without value label - adds stories and documentation to docs page - adds additional migration guide context to CHANGELOG
- removes some duplicative docs language for pgoress bar - adds correct punctuation to CHANGELOG - passes default value for customWidth in args for progress bar - uses passive voice in meter documentation - removes repetitive StaticWhiteDocs story in favor of previous StaticWhite story - removes Chromatic snapshot for WithoutLabel progress bar story
0bf91c5
to
e6a7dc2
Compare
Description
This continues the effort to migrate documentation from the CSS static docs site into Storybook, with a focus on
progressbar
andmeter
.meter
andprogressbar
.progressbar
also now has ashowValueLabel
control to better align with the ability to show that value label or not, according to guidance documentation.This PR has no CSS changes, so no changeset is needed.
Jira/Specs
CSS-937
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