Improve Drupal UX for Staff Profile, VAMC Billing & Insurance, VAMC Facility mental health phone number

[davidmpickett]

[2024-10-16] Not blocking shipping CMS changes behind a toggle, but IS launch blocking for change management / editor comms.

Description

These three content types are changing from a single non-required field to a paragraph type for phone number entry

• Staff Profile
• VAMC System Billing & Insurance
• VAMC Facility - (Mental Health Phone Number)

Current UX quirks

When a phone number has been added, it's not immediately clear how to remove it. There's also a bunch of irrelevant options in the menus like Collapse and Drag & Drop. We also repeat the "phone number" title.

When no phone number has been added there's a weird gap with a bullet point in it. And there's the awkward phrase "add phone number to phone number"

Change log

• Staff Profile now defaults to no phone number (but can be manually added)
• The widget for all three content types has changed from Paragraphs Stable to Paragraphs Legacy

State	Current UI	New UI
No phone number added
With phone number added

Acceptance criteria

ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable.

• Implement new interface for each Content Type

[jilladams]

In sprint 15: Jordan may not have time to address before Dave is back from PTO

The conversation from scrum: https://dsva.slack.com/archives/C079GFKN50D/p1729007496363379?thread_ts=1728955309.898119&cid=C079GFKN50D

Staff Profile = guess: ~75% of those have #s
Mental Health Phone = should feel required (or be required)
Billing & Ins = need to audit to know which way to handle

All 3 don't have to act the same.

This does not block merging existing phone # work to prod behind the feature toggle.

[jilladams]

Pointing as a 5 based on Jordan's level of familiarity. May be lower if Dave picks it up.

[davidmpickett]

@jilladams Is this in Sprint or Needs refinement?

[davidmpickett]

WIP notes to self

VAMC System Billing & Insurance

• Current total published = 139
• How many with phone number? 132/139 = 95%
• FE expects this to exist - it's conspicuously absent when left empty
• https://www.va.gov/asheville-health-care/billing-and-insurance/
• https://www.va.gov/fayetteville-coastal-health-care/billing-and-insurance/
• https://www.va.gov/hampton-health-care/billing-and-insurance/
• https://www.va.gov/salisbury-health-care/billing-and-insurance/
• https://www.va.gov/lovell-federal-health-care-va/billing-and-insurance/
• https://www.va.gov/louisville-health-care/billing-and-insurance/
• https://www.va.gov/manchester-health-care/billing-and-insurance/

VAMC Facility - (Mental Health Phone Number)

• Current total published = 1285
• How many with phone number? 1078/1285 = 84%
• What happens on FE when absent? = Graceful degradation
• Probably should have a number
  • https://www.va.gov/indiana-health-care/locations/brownsburg-va-clinic/
• probably correct to not have a number
  • https://www.va.gov/columbia-south-carolina-health-care/locations/columbia-va-mobile-clinic/
  • https://www.va.gov/central-western-massachusetts-health-care/locations/plantation-street-va-clinic/

Staff profile

• Current total published = 6034
• How many with phone number? = 4655 = 77%
• What happens on FE when absent? = Graceful degradation
• https://www.va.gov/lovell-federal-health-care-va/staff-profiles/robert-buckley/
• https://www.va.gov/lovell-federal-health-care-va/staff-profiles/chad-roe/

[davidmpickett]

I think the solution is gonna be switching to Paragraphs Legacy widget

[davidmpickett]

End of Sprint update

• PR has ✅ code review and ✅ UX review (slack thread)
• Waiting to hear from @laflannery if a11y review is needed
• Other than that ready to merge & verify

[davidmpickett]

Update

• I have moved this back to In Progress to incorporate @laflannery's notes in the PR
• Because the new scope of Laura's edits require modifying the SCSS, I am also gonna fix the Truncated textissue @jilladams caught
• Will need to go through testing and code review again & now need review by CMS platform team