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

[V3 Components] Opt-out of V3 components #16976

Closed
1 task
Tracked by #17059
FranECross opened this issue Jan 23, 2024 · 3 comments
Closed
1 task
Tracked by #17059

[V3 Components] Opt-out of V3 components #16976

FranECross opened this issue Jan 23, 2024 · 3 comments
Assignees
Labels
Public Websites Scrum team in the Sitewide crew sitewide V3 Components Update to V3 VA.gov frontend CMS team practice area

Comments

@FranECross
Copy link

FranECross commented Jan 23, 2024

Description

The Design team will be migrating all V1 components to V3 components on February 16th, which doesn't provide the Public Websites team adequate time to implement V3.

This ticket is to implement opting out of V3 components so that we can prioritize the tickets implementing V3 for components currently using V1.

For products not using any components, we'll prioritize those at a later date, or as those products are being enhanced/changed in the future.

V1 components that need to be opted out of

  • Accordion: Used in
    • CLPs
    • Benefits Landing pages
    • Benefits Detail Pages
    • Income Limits
    • PACT Act
    • FAQ page
    • Resources & Support Detail page
  • Additional Info
    • Income Limits
    • PACT Act
  • Alert: Used in
    • Benefits Landing pages
    • Benefits Detail pages
    • Income Limits
    • Discharge Upgrade
    • Global Search Results
    • Find a Form
    • Resources & Support Detail page
    • FAQ page
    • BTSSS login widget
  • Button: Used in
    • Income Limits
    • PACT Act
  • Button Pair: Used in
    • Income Limits
    • PACT Act
  • Number Input: Used in
    • Income Limits
  • Radio Button: Used in
    • Discharge Upgrade
  • Select: Used in
    • Income Limits
    • Discharge Upgrade
    • Find a Form
  • Modal: Used in
    • Find a Form
  • Pagination: Used in
    • Resources and Support Results
    • Events
  • Search Input: Used in
    • Homepage
    • Find a Form

For reference, The other v3 components that exist but I do not believe we are using their v1 equivalents anywhere at this time are:

  • Breadcrumbs
  • Featured Content
  • Checkbox
  • Memorable date
  • Privacy Agreement
  • Progress bar - Segmented
  • Statement of Truth
  • Text input
  • Textarea
  • Process List

Documentation

User story

AS A PO/PM for Public Website products
I WANT to opt-out of the V3 component migration for some or all of our products currently using V1 (final list TBD after assessment)
SO THAT we have time to switch from V1 to V3

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

  • All V1 components with V3 correlates are opted out of the V3 update on Feb 16th.
@randimays
Copy link
Contributor

Status update: the vets-website PR has been merged and I am verifying in staging. I am waiting on a PW review for the content-build portion so I can merge that into staging. Hoping to get both pieces to production today.

@randimays
Copy link
Contributor

content-build has been merged into prod 👍🏻 vets-website is having some CI issues and many merges have not yet made it to prod since yesterday. I'm waiting on that to resolve to do a quick validation and call this done.

@FranECross FranECross added the V3 Components Update to V3 label Feb 7, 2024
@randimays
Copy link
Contributor

This was held up for a couple days while Platform triaged the ongoing CI issues with vets-website. They were able to resolve them yesterday afternoon, so the v3 opt-outs for vets-website are in production and good to go! Closing!

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 V3 Components Update to V3 VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

3 participants