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
Consider adding an ASIDE component to the design system #258
Comments
Cross-linking @sporeboy comment from VA.gov issue 2172:
|
ooh so is this going to be tested again soon with "View Payments" @sporeboy? BAM2 ended up changing their design to not include the right rail. If it's going to be tested again soon make sure to include me when writing the conversation guide and chatting about the study |
when you say "it is used on lots of pages" @cohnjesse are there others you've identified besides Claim Status Tool and the tools that you all have created on eBenefits? Just so I'm aware of the places we have it currently and can inform folks. I remember the history here when Jeff Barnes initially brought it up as a design he wanted the team to use. |
ah it's on Search too https://www.va.gov/search/?query=agent+orange |
Note: guidelines are being developed by @rtwell and @sshein as per #160 (comment) |
Feature Request
Is this feature request relating to an existing component or utility? Please describe.
Do you have a suggestion for a new component or utility?
Jesse on the eBenefits team has created two important items for this component
Additional context
I (Trevor) am trying to work this into our council process, with the understanding it hasn't been socialized to developers yet. I need additional help to decide if this is a component we want to add to the design system, and to make sure it's feature-complete before being merged and put into production.
I have added myself to the pull request and have some changes to suggest, and would like to see documentation thought out for the aside. At a minimum:
<main>
component, but as a peer/cc @KevinMHoffmanUSDS && @CrystabelReiter
The text was updated successfully, but these errors were encountered: