Address pattern

[megzehn]

• [ ] Update csv with labels & errors (Megan & Laura)
• [ ] Update mock pattern library screen (Jeana)
• [ ] Send Matt csv & screenshot of mock pattern (Megan & Laura)
• [ ] Update related Figma files (someone)

[humancompanion-usds]

• Update CSV or JSON with labels & errors and in future, content
• Push that data (CSV of JSON) into Figma via a plugin (that we need to play around with)
• Design System Team (DST) will create the Figma component variations
• Design System Team (DST) will update the pattern template as needed, and with direction from CAIA
• Veteran-facing Forms Team updates codified patterns as needed in the Forms Library and updates the examples in the mocked patterns.

[megzehn]

Questions for address pattern page:

What are the main reasons we separate a Single address layout from the Multiple addresses layout? The layouts are nearly identical, aside from the header and explainer body text on the Multiple address layout. But I think in most cases, we probably still want the header and body explainer text even if we're just asking for one address. This is the case in the mock form pattern.

[megzehn]

Under content considerations

Could we reorder and relabel the fields like this?

• Label
• Hint text:
• Error type 1:
• Error message 1:

Could we group all errors types and error messages together for a single field?

• Postal code
• Hint text: None
• Error type 1: No entry
  • Error message 1: Enter a postal code
• Error type 2: Incorrect entry
  • Error message 2: Enter a valid 5- or 9-digit zip code (with or without dashes)

Could we add a "notes" line on fields that have known variations?

• Street address
• Label variations: Apartment or unit number

[megzehn]

[Editing this comment to link to a PR instead]

@humancompanion-usds, I created this PR with label updates for addresses. Could you review and merge when you can?