-
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
[SPIKE] Discover where in Public Websites managed products/features/apps we need to accommodate migration onto va-icon #17744
Labels
Public Websites
Scrum team in the Sitewide crew
sitewide
VA.gov frontend
CMS team practice area
va-icon
Comments
Pulling in as Stretch on 4/11 |
Tickets created (@FranECross feel free to edit as needed!):
Epic: #17738 Closing this ticket as complete. |
Excellent, @randimays ! Thanks so much! |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Public Websites
Scrum team in the Sitewide crew
sitewide
VA.gov frontend
CMS team practice area
va-icon
Description
This spike is to discover and list out which features/apps/products will be affected and need work done in order to accommodate the migration to va-icon, and deprecation of Font Awesome.
User story
AS A PO/PM of Public Website managed apps/features/products
I WANT to understand the scope of work necessary to migrate to va-icon and accommodate the deprecation of Font Awesome
SO THAT I can prioritize the work and meet the (tentative) deadline of end of May 2024
Artifacts
Engineering notes / background
Analytics considerations
Quality / testing notes
Acceptance criteria
The text was updated successfully, but these errors were encountered: