department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Discovery Research Epic: Reusable Form Wizard #10182

Closed mchelen-gov closed 4 years ago

mchelen-gov commented 4 years ago

High Level User Story

As a frontend developer, I need a reusable form wizard component so I can implement multi-choice user workflows in quick and standards-compliant way.

Goals

What outcome(s) do we want to see? A well defined and documented standard approach to frontend multi-choice forms with conditional logic.

Background

There is a wizard pattern documented on https://design.va.gov/patterns/wizards which points to multiple code examples with various implementations. One of these examples is How to file a VA disability claim(source code) which uses a <Wizard> component. This component was created for a particular use case, and may or may not be suitable for reuse. It is not published as a Formation component.

A frontend engineering team was tasked with creating a multi-path form for the Coronovirus Screener app (source code). Because of the urgent need for deployment of the app and lack of clarity around a standard approach, code may have been written which is redundant with other solutions.

Next Step

Determine which of these approaches to pursue:

  1. Document and publish the <Wizard> component to Formation and
  2. Adapt the Coronovirus Screener code to be reusable
  3. Identify and document a 3rd party library as the standard for this use case

Issues to create within this Epic

- Create research plan
- Recruit for research sessions/Schedule research sessions
- Create conversation guide
- Conduct Discovery Research Sessions (at a minimum, the team lead, PM, designer, content person should join these sessions).
- Discovery Synthesis - should be conducted as a team, led by designer.
- Discovery Research Readout (at minimum, it is expected that the designer should do a readout at design meetings & for their team. If stakeholder readouts are needed, the team lead/PM are responsible for scheduling those. Designers should also plan to do research readouts at the end-of-sprint demo.)

How to configure this issue

mchelen-gov commented 4 years ago

closed in favor of https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/192