Audit uses of font-awesome for va-icon replacement

[jilladams]

Goal: va-icon adoption (Design System Team Initiative for all teams):

Font Awesome will be deprecated. The DST is working on guidance for how teams can migrate onto va-icon. They tentatively expect Font Awesome to be deprecated at the end of May 2024

We need to audit usage in the facilities product, to understand scope of getting these changed.

DS guidance (WIP): https://design.va.gov/storybook/?path=/docs/uswds-va-icon--default

Scope & Notes

Probably in both content-build and vets-website?

All font-awesome icons appear in <i> tags. They're everywhere.

Correlated Public Websites work, for reference: (Randi = POC)

• Audit: [SPIKE] Discover where in Public Websites managed products/features/apps we need to accommodate migration onto va-icon #17744
• Epic: PW: [EPIC] Migrate off of font-awesome for iconography; deprecation of Font Awesome  #17738 -- contains tickets created as a result of the audit

ACs

• Facilities products are audited for font-awesome use, and
  • VAMC (systems, facilities, top task pages)
  • Vet Centers
  • Facility Locator
  • Facility Locator detail pages
  • Regional Offices (pre-prod templates)
• tickets are cut for FE work to update products in whatever way makes sense to FE folks
• Schedule calendar time with Jill, Michelle (required) and DaveP (optional) to review audit findings, and determine priority for Sprint 2 injection vs. Sprint 3

[jilladams]

Facility Locator detail pages are generated from the API, but we don't think we've touched them.
Contained under the Facility Locator app, per Eli.

@laflannery to take a look re: V3 components to make sure we haven't overlooked components on those.

[jilladams]

Eli: would be ok with one ticket to replace font-awesome usage across all our products in both repos.
But: bigger testing burden.
3 for content-build, 3 for vets-website maybe for implementation, tbd DS guidance / how many invocations
The replacement params will affect scope: may include style changes, will depend on what the va-icon spec is.

[jilladams]

Mapping from Font-awesome sizes (S, M, L), to DS component (3-9) may be a sizable piece of the work.

[eselkin]

It seems that only a few places in the current font awesome inclusions use sizes. Those are not any of our Facilities products.

[davidmpickett]

@jilladams Do you want to tag this with Sprint 1 since it technically started before Sprint 2? Or just do Sprint 2 since it wasn't part of Sprint 1 commitment? Not sure what your preference for reporting is

[jilladams]

Thanks Dave - Added sprint 1

[eselkin]

Tickets created:
VAMC content-build and vets-website in one ticket: #17855
Vet Center and Vet center Locations in one ticket: #17874
Facility Locator and Detail Pages in one ticket: #17884
VBA: #17886

[eselkin]

@jilladams All tickets created

[davidmpickett]

Added all tickets to the epic: #17722

[jilladams]

Laura, Michelle, Eli and I reviewed. @laflannery to handle one cleanup piece where va-link component adoption needs to be handled within these icon tickets.

Otherwise: tickets are mostly refined, remaining cleanups on refining are added to team refinement ticket, and we've kicked off a conversation with the DS around what happens next. Closing!