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

[V1 & 3 Components] Implement available components for Event Detail page #17057

Closed
6 tasks done
laflannery opened this issue Jan 26, 2024 · 1 comment
Closed
6 tasks done
Assignees
Labels
Public Websites Scrum team in the Sitewide crew sitewide V3 Components Update to V3 VA.gov frontend CMS team practice area

Comments

@laflannery
Copy link
Contributor

laflannery commented Jan 26, 2024

Background

The Design team is releasing a Typography update (sometime in March), which means that the PW team needs to upgrade any of our products where components aren't currently being using, but a V1 or V3 component is available.

If the updates aren't made prior to the Typography update, there's a chance that Veteran-facing issues may occur.

The following have been identified by Laura Flannery:

Example Pages:

List of Components

Elements that are not using components that should be (Backlog)

  1. Link
    • We should be using this everywhere possible
  2. Accordion
    • On recurring events, there is an accordion to show more times which should use the v3 component

Documentation

Sitewide V3 DS component review spreadsheet

User story

AS A PO/PM for Public Websites products
I WANT to implement available V1 or V3 components in features & products currently under Public Websites management where components aren't currently being used
SO THAT all PW products are in alignment with the current component version
AND Veterans and other users have a consistent experience throughout VA.gov tools and information

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

  • Links are using V1
  • Accordion is using V3
  • other features display correctly
  • verify/review the E2E tests
  • check desktop and mobile
  • a11y review
@laflannery laflannery added Needs refining Issue status VA.gov frontend CMS team practice area Public Websites Scrum team in the Sitewide crew and removed Needs refining Issue status labels Jan 26, 2024
@FranECross FranECross added Needs refining Issue status V3 Components Update to V3 labels Jan 31, 2024
@FranECross FranECross changed the title [V3 Components] Upgrade V1 components to V3 for Event Detail page [V3 Components] Implement available V3 components for the Event Detail page Feb 13, 2024
@FranECross FranECross changed the title [V3 Components] Implement available V3 components for the Event Detail page [V3 Components] Implement available components for the Event Detail page Feb 15, 2024
@FranECross FranECross changed the title [V3 Components] Implement available components for the Event Detail page [V1 & 3 Components] Implement available components for the Event Detail page Feb 15, 2024
@laflannery laflannery changed the title [V1 & 3 Components] Implement available components for the Event Detail page [V1 & 3 Components] Implement available components for Event Detail page Feb 19, 2024
@FranECross FranECross removed the Needs refining Issue status label Feb 28, 2024
@randimays randimays self-assigned this Mar 18, 2024
@randimays
Copy link
Contributor

Verified successfully in prod. 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

4 participants