-
Notifications
You must be signed in to change notification settings - Fork 71
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
Comments
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? |
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? |
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 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 |
Technically: Public Websites owns both:
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 |
Also I might just be repeating what Laura already knew. |
@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:
The fact that everything is named the same but refer to different things is where I think the mud comes into play |
@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: ![]() Based on that, I'm not sure if we own this (or if it's useful anywhere else). Any thoughts? |
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! |
Restating / Noting again since I keep forgetting, from discussion with Laura:
|
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 convertedThe text was updated successfully, but these errors were encountered: