-
Notifications
You must be signed in to change notification settings - Fork 16
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
Remove "Usage" section of design.login.gov #228
Conversation
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
README.md
Outdated
@@ -81,3 +89,94 @@ Before starting, make sure that all changes intended for release should be merge | |||
- The release version should match the version just published to `npm` (for example, `v2.1.5`). | |||
- Use the version name as the release title. | |||
- Use the release notes to link to any important issues or pull requests that were addressed in the release. You may copy this from `CHANGELOG.md`. | |||
|
|||
## Use with Rails |
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.
Would it make sense to group the two "Use with/as" headings under a "Usage" heading? Maybe also the Jekyll plugin if we reincorporate it per Zach's comment.
e.g.
## Usage
...
### Use with Rails
...
### Use as a JavaScript package
...
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 dig it 20933ae
* Remove custom Accordion close button element **Why**: Maintenance: - Limit divergence from USWDS, facilitating ongoing maintenance and reducing potential confusion introduced by enhancements exclusive to the login.gov Design System. Accessibility: - The button's behavior is duplicative with the toggle, where the additional tab stop may be excessive as repeated content. - Collapsing an accordion by the close button causes a focus loss ([SC 2.4.7](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html), [SC 2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html)) - The relationship between the button and controlled content is not clearly indicated (e.g. [`aria-controls`](https://www.w3.org/TR/wai-aria-1.1/#aria-controls)) * Remove unused variable $icon-size * Restore border radius to accordion content bottom border * Clarify removal of JavaScript exported member
Co-authored-by: Andrew Duthie <[email protected]>
Co-authored-by: Andrew Duthie <[email protected]>
Co-authored-by: Andrew Duthie <[email protected]>
Co-authored-by: Andrew Duthie <[email protected]>
@aduth updates made. Re-requested review before 🚀 please 😄 |
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.
Looks good 👍
("Files changed" look like they include changes from #229, but pretty sure that should merge cleanly)
This pull request transitions "Usage" of the design system from living on design.login.gov as a
.md
file to being part of the README. As the user is primarily internal team members, it makes sense to keep this installation and usage information in one place (instead of two).