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

FE: Determine which PW products need updates to web components #16871

Closed
3 tasks
randimays opened this issue Jan 17, 2024 · 3 comments
Closed
3 tasks

FE: Determine which PW products need updates to web components #16871

randimays opened this issue Jan 17, 2024 · 3 comments
Labels
Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area

Comments

@randimays
Copy link
Contributor

randimays commented Jan 17, 2024

Description

On February 16, all design system web components will default to their v3 variant. v3 will be opt-out only. Current PW product status regarding web components:

  • Some products use some v3 web components
  • Some products don't use web components but can/should
  • Some products use web components, but they are not v3

To align with brand standards and maximize compliance with accessibility requirements, we need to update as many of our products as possible to use v3 web components. It is anticipated that this ticket will include a review of both vets-website and content-build code.

Slack thread for v3 update announcement: https://dsva.slack.com/archives/C03R5SBELQM/p1705503589174489
List of PW products: https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/public-websites

This ticket is intended for discovery only as design/functionality may change for new web components and we want to ensure thorough testing and design approval.

User story

Describe the audience/user, enhancement or fix, and value / outcome desired.

AS A
I WANT
SO THAT

Acceptance criteria

@randimays randimays added Needs refining Issue status Public Websites Scrum team in the Sitewide crew VA.gov frontend CMS team practice area labels Jan 17, 2024
@FranECross FranECross removed the Needs refining Issue status label Jan 17, 2024
@jilladams
Copy link
Contributor

I started this process today: https://docs.google.com/spreadsheets/d/1A7mQMnL2d5JcDKHZ2daVYQVr85qOljrwM0aUk_inO88/edit#gid=0.

Based on 1 example of each content type that has a veteran-facing page, used the handy dandy plugin Laura shared here, and noted the components I saw in use.
This isn't comprehensive, as some markup may not appear if content isn't populated fully in Drupal, etc. But a starting point.

@randimays
Copy link
Contributor Author

@jilladams @FranECross is it safe to say this is complete?

@jilladams
Copy link
Contributor

Yep.

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
Projects
None yet
Development

No branches or pull requests

3 participants