Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sitewide Alerts: upgrade to va-icon #17818

Closed
4 tasks
randimays opened this issue Apr 11, 2024 · 9 comments
Closed
4 tasks

Sitewide Alerts: upgrade to va-icon #17818

randimays opened this issue Apr 11, 2024 · 9 comments
Labels
Full-width alert CMS managed product co-owned by Facilities & Public Websites teams Promo banner CMS managed product owned by Public Websites team Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area VA.gov Search Search.gov integration, owned by Public Websites team va-icon

Comments

@randimays
Copy link
Contributor

randimays commented Apr 11, 2024

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/p1710776364414359

We 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--default

Engineering notes

Icons to be converted:

  1. https://github.com/department-of-veterans-affairs/vets-website/blob/17621d7d0b4c4a3df774bd3a742aeda72cdae797/src/platform/site-wide/alerts/MobileAppCallout.jsx#L39
  2. https://github.com/department-of-veterans-affairs/vets-website/blob/17621d7d0b4c4a3df774bd3a742aeda72cdae797/src/platform/site-wide/alerts/MobileAppCallout.jsx#L54

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

  • Spot check of all converted icons on mobile and desktop
  • Update any unit / e2e tests where applicable

Acceptance criteria

  • a11y review
  • all instances of <i> that can be converted to <va-icon> are converted
@randimays randimays added Needs refining Issue status Public Websites Scrum team in the Sitewide crew VA.gov frontend CMS team practice area and removed Needs refining Issue status labels Apr 11, 2024
@jilladams jilladams added VA.gov Search Search.gov integration, owned by Public Websites team Promo banner CMS managed product owned by Public Websites team Full-width alert CMS managed product co-owned by Facilities & Public Websites teams labels Apr 11, 2024
@jilladams
Copy link
Contributor

Q here: Ticket is for Alerts but code refs are for Search. Just want to confirm that full width banners and promo banners were also considered re: whether they have any icons to replace?

@randimays
Copy link
Contributor Author

Darn, I must've been having some clipboard issues. I updated the links in this ticket to the correct ones 🔍

Promo banners that use the v3 web component are already covered by the DST upgrading their own icons: https://design.va.gov/components/banner/promo.

I think full width banners are Facilities-specific (per this Slack thread); but could use a sanity check there. @laflannery?

@laflannery
Copy link
Contributor

Ok I had to go back to @randimays on this cause to many things called banners. The end result is that PW alerts are all using the banners template which Randi indicated in her above comment us DS component so icons will come along for the ride.

There is another file fullwidth_banner_alerts that is used by Facilities that is custom code and will need to be handled by that team

@jilladams
Copy link
Contributor

Technically: Public Websites owns both:

  1. Full Width Alerts (banners in drupal machine language) -- these are the ones that show at page top when they're live.
  2. Promo Banners (promo_banner in Drupal machines) -- these show at page bottom.

Facilities has adapted the use of Full Width Alerts as the backbone of VAMC System Banner Alert with Situation Updates. So the icons on that may come along for the ride.

Let me know if that makes everything perfectly muddy again. :D

@jilladams
Copy link
Contributor

Also I might just be repeating what Laura already knew.

@laflannery
Copy link
Contributor

@jilladams What I was referring to and linked above above are Github files, not content types in Drupal and I think that's where the split in ownership is:

  • PW owns the Full Width Alerts content type in Drupal use the banners Github file to render these on the front end
  • Facilities on the other hand owns System banner alerts and they use a Github file named fullwidth_banner_alerts to render these.

The fact that everything is named the same but refer to different things is where I think the mud comes into play

@randimays
Copy link
Contributor Author

randimays commented Apr 15, 2024

@jilladams @laflannery More muddiness: this ticket is only for the Mobile App Callout banner in vets-website (not related to anything Drupal-y).

I dug into it a bit more, at first thinking that because it's in the site wide folder in vets-website, it's used for many things. It's actually only used for a single authenticated page at the moment: The blue banner at the bottom of this screenshot:

Screenshot 2024-04-15 at 10 04 54 AM

Based on that, I'm not sure if we own this (or if it's useful anywhere else). Any thoughts?

@jilladams
Copy link
Contributor

As far as I'm aware, we do not own that. I feel comfortable closing this as no op based on that. Reopen if I'm missing something!

@jilladams
Copy link
Contributor

Restating / Noting again since I keep forgetting, from discussion with Laura:

  1. Full Width Alerts (banners in drupal machine language) -- already uses a component, DS will handle icon updates
  2. Promo Banners (promo_banner in Drupal machines) -- already uses a component, DS will handle icon updates
  3. VAMC System Banner Alert with Situation Updates (full_width_banner_alert) -- doesn't use a component, needs to, needs custom work. May be affected by font-awesome deprecation. Work is captured in VAMC System (incl banners): adopt V1 and V3 components where components are not used #16952

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Full-width alert CMS managed product co-owned by Facilities & Public Websites teams Promo banner CMS managed product owned by Public Websites team Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area VA.gov Search Search.gov integration, owned by Public Websites team va-icon
Projects
None yet
Development

No branches or pull requests

4 participants