[EPIC] Standardize phone number entry in Drupal interfaces

[jilladams]

Update 7/18/2024: Renaming this epic to better reflect the specific set of work we will be tackling and changing to be Sitewide rather than Facilities - @davidmpickett

Background

Historically we allowed Drupal editors to enter phone number into a phone number Field field_phone_number that allowed for a wide range of input. (This is on VAMC facilities primarily. VAMC Health Services already use the phone number paragraph type, and will not be addressed in this epic.)

We later developed the phone number Paragraph Type paragraphs_type/phone_number which breaks down the components of phone numbers into separate input fields so that the FE can better parse the data and pass it to the Design System Component.

Example of phone Field

Example of phone Paragraph Type

The Work

• Updating various Drupal interfaces to use the Paragraph Type instead of the Field
  • Migrating existing data
  • Updating Drupal interface
  • Updating FE query and template
  • Removing old Drupal field
• Upgrading the Phone Number Paragraph Type to handle additional use cases
  • Better validation of sub fields like Extension
  • New sub fields like Vanity & International

The Impact

• Allows us to finish Design System component adoption on our products
• Improves guardrails in Drupal to prevent editor errors
• Results in more reliable experience for Veterans on various products

[davidmpickett]

@Agile6MSkinner @mmiddaugh @jilladams I want to note that while the tickets that are in this epic are tightly scoped around improving one Drupal "component" across multiple products, this epic also currently includes another epic which is very product specific (Mental Health Phone Numbers).

Would be good to clarify if the remaining parts of #9717 are part of the Q3 priority, or if that's just a vestige of how we originally organized this.

Edit I went ahead and made that change and also retitled this epic so it can include non-facilities tickets like #17326

[davidmpickett]

Brief notes from a prefinement meeting today:

• We think it make sense for @jv-agile6 to be the primary engineer for this epic (with copious support)
• The question of whether it makes sense to do 17861 or 17863 first is really a matter of preference rather than necessity
• @davidmpickett structured 17861 to have a comprehensive view of both the Drupal and FE work required. That may or may not be the way that makes sense to do it, might end up being broken back down into Drupal and FE
• Additional engineering conversations will happen to further refine tickets
• Once a pattern is established for 17861, that should be applied to other tickets in this epic