[UX] 10-10EZR NOK/EC: Update the design for the List&Loop pattern

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

281 stars 197 forks source link

[UX] 10-10EZR NOK/EC: Update the design for the List&Loop pattern #90399

Open IMHieuVo opened 1 month ago

IMHieuVo commented 1 month ago

Issue Description

Currently, Veterans can only VIEW their Emergency Contact information and Next of Kin information on the Profile and Check-in flow. Adjacent team research shows that Veterans strongly desire a way to edit their NOK/EC information.

This work is to add Emergency Contact (then Next of Kin) into the EZR flow so there is a place for Veterans to edit this information.

We will utilize the recent release of Form Library's List & Loop pattern.

References/Resources

Tasks

[x] Refresh the NOK/EC with the EZR team
[x] Update designs and references in Figma with capture notes and callouts
[x] Review with UX team and align changes with EZ/CG
[x] Make adjustments + additional pattern investigation
[ ] Review with EZR team

Acceptance Criteria

The designs using the latest design system guidance and aligned with EZ.

IMHieuVo commented 1 month ago

Aug 8, Team Refresher summary:

Hieu presents an overview of the project: why we're doing this, where it will be located, and how it aligns with our EZR v2.
The EZ/CG team is doing adjacent work with insurance information using the next list & loop pattern. We'll be sharing notes.
Hieu shows the graphical out-of-the-box list & loop pattern and Devs notes that the current vs changes comparison in recent projects has been helpful.
Action Item: Hieu to create a comparison between out-of-box vs our version.
Hieu notes that the text and icon can be changed, Save-in-progress works, and conditional (in theory) should be possible.
Josh notes that this work is try-quickly and fail-quickly approach. Devs show hesitation since EZ is also doing similar work and would be 'failing' as well.

IMHieuVo commented 3 weeks ago

Aug 20 Design Office Hour summary, regarding list & loop component:

Visual changes are not a big deal, proceed with frontend since it does not change how they are coded.
Team should connect with Jeana Clark when they diverge from the Forms pattern
Platform is okay with differing versions (Forms vs Custom) as long as it is not on the same page and there is an intent to update the Custom at a later date. It will not be a launch blocker.
Platform will now call out custom List & Loop in their reviews.

emily-brown34 commented 6 days ago

content/design is fine with the emergency contact fields NOT being labeled primary and secondary