Open randimays opened 3 weeks ago
Mid-sprint update: we have been blocked on using va-icon in content-build since 4/19. DST is still working on a fix; it's not clear whether it will be released before the end of our sprint, but flagging the risk here.
Description
The Design System team is deprecating Font Awesome and encouraging teams to use
<va-icon>
where possible by the end of May 2024. Slack post here: https://dsva.slack.com/archives/C03R5SBELQM/p1710776364414359We need to convert all usage of
<i>
in this application to<va-icon>
to align with the icons in DST's library here: https://design.va.gov/foundation/icons<va-icon>
guidance in Storybook: https://design.va.gov/storybook/?path=/docs/uswds-va-icon--defaultEngineering notes
Icons to be converted:
User story
AS A PO/PM for products/features/applications managed by the Public Websites team I WANT our features/products/applicates migrated to va-icon where appropriate SO THAT when the migration to va-icon and deprecation of Font Awesome takes place, there won't be degraded Veteran-facing experiences in VA.gov.
Quality / testing notes
Acceptance criteria
<i>
that can be converted to<va-icon>
are converted