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

PW: [EPIC] [V1 & 3 Components] Implement available components in PW products where components aren't currently used #17078

Closed
1 task
Tracked by #17336 ...
FranECross opened this issue Jan 29, 2024 · 3 comments
Assignees
Labels
CY24-Q3 Sitewide Q3 initiatives Epic Issue type 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 29, 2024

Status

[2024-03-013] Good progress made; 7 completed out of 20

[2024-02-29] Out of 20 tickets:

  • 3 Completed
  • 1 Blocked
  • 16 are in Refined and ready to be worked on

Description

The Design team is releasing a Typography update in Mid-April, 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.

  • Design Team's Typograph epic
  • Discovery work is on Confluence. I've asked (3/6/2024) if they can export to a PDF.

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

User story

AS A PO/PM for Public Websites products
I WANT to implement available V1 and 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 within VA.gov

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

  • See the individual stories for AC
@FranECross FranECross added VA.gov frontend CMS team practice area Epic Issue type Needs refining Issue status Public Websites Scrum team in the Sitewide crew labels Jan 29, 2024
@FranECross FranECross added the V3 Components Update to V3 label Feb 8, 2024
@laflannery
Copy link
Contributor

Adding important applicable deadlines:

  • Typography update (which has the potential to possibly break elements that currently aren't using components) is happening most likely "next month". Matt Dingee has said there will be a more formal announcement when there is more info to share but this is currently what we know

Slack thread for reference

@FranECross FranECross changed the title [V3 Components] Implement available V3 components in PW products where components aren't currently used [V1 & 3 Components] Implement available components in PW products where components aren't currently used Feb 15, 2024
@FranECross FranECross changed the title [V1 & 3 Components] Implement available components in PW products where components aren't currently used [EPIC] [V1 & 3 Components] Implement available components in PW products where components aren't currently used Feb 26, 2024
@FranECross FranECross removed the Needs refining Issue status label Feb 27, 2024
@FranECross FranECross self-assigned this Feb 27, 2024
@FranECross
Copy link
Author

@chriskim2311 @randimays I've added a link in the Description to the Design Team's epic (Thanks @jilladams ).

@jilladams jilladams changed the title [EPIC] [V1 & 3 Components] Implement available components in PW products where components aren't currently used PW: [EPIC] [V1 & 3 Components] Implement available components in PW products where components aren't currently used Jun 6, 2024
@FranECross FranECross added the CY24-Q3 Sitewide Q3 initiatives label Jul 8, 2024
@jilladams
Copy link
Contributor

Closing. The remaining work is in its own epic (#17557 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CY24-Q3 Sitewide Q3 initiatives Epic Issue type 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