-
Notifications
You must be signed in to change notification settings - Fork 148
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
Build new components landing page and simplify component docs templates #1136
Conversation
…dw-reorganize-components
_components/button-group/guidance/variants/default/accessibility.md
Outdated
Show resolved
Hide resolved
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.
Code samples seem to be extending beyond bounds of accordion in some components.
You can see this on Prose for example.
|
OK, I think I've fixed all these issues! |
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.


Hold is no longer necessary. Changed base to 2.11.0 release branch.
Preview →
Paired with uswds/uswds#4056
Accessibility requirements
Ensure component page landmarks are unique. Ensure component page landmarks are unique. #1109NOT FIXED HERETODO
Fixes #1091 [Adds variant information to data]
Fixes #1110 [Removes scope from
tdelements]Fixes #1108 [Heading order]
Fixes #1088 [Banner/identifer core components notes]
This PR restructures and re-organizes both individual component pages and the components overview page.
ComponentsandPackagesForm controls_layouts/component.htmltemplate to power all component pages[component]/guidance/...Markdown filesComponent front matter
category
component
implementation
lead
permalink
redirect_from
subnav
title
tags
title
type
...
I gave up trying to document it all... :(