department-of-veterans-affairs / vets-design-system-documentation

Repository for design.va.gov website
https://design.va.gov
37 stars 57 forks source link

[Documentation] - Multiple responses pattern #3219

Open babsdenney opened 3 weeks ago

babsdenney commented 3 weeks ago

Description

@jeana-adhoc Found some outdated information and screenshots on the multiple responses page. We need to update the documentation for the multiple responses. See the comment below for more details.

To do

Look through these experimental design request in the backlog to see if any of the work overlaps with these tickets

Details

Be sure to use the appropriate maturity scale option. If this is a new component that has not yet gone through Staging Review, use the "Use with Caution: Candidate" label.

Tasks

Acceptance Criteria

caw310 commented 3 weeks ago

Hey team! Please add your planning poker estimate with Zenhub @babsdenney @danbrady @LWWright7

jeana-adhoc commented 2 weeks ago

Looking at the VADS Documentation for "Multiple Responses Pattern" here are my concerns...

Below the heading "How to design and build - Single page" there is an alert that reads

This single-page variation is currently used on VA.gov, but is no longer the preferred variation for this pattern. The multi-page pattern is recommended for new designs.

And screen shots follow that match the pattern that is no longer the preferred variation. Those screenshots match what is currently documented in the figma link at the top of the documentation page.

Those screenshots I think should go away if that's no longer the preferred pattern. And the figma files should not be made available either.

I do have figma files for the new pattern here. Since it's a full multi-page pattern complete with summary page, and modals, I'm not sure the best way to include it in a library, and would be willing/open/able to help out to transform this into something more usable as part of the VADS Templates, Patterns, and Forms library.

caw310 commented 1 day ago

Moving to the next sprint in place of #3278 which is needed before development on #3274 can be done which is a launch blocker.