[V1 & 3 Components] Upgrade V1 components to V3 for Resources & Support taxonomy term page

[FranECross]

Background

The Design team is migrating all V1 components to V3 on February 16, 2024, which means that the PW team needs to upgrade any of our products currently using V1 components to V3.

Example pages:

• VA account and profile
• Education and training

List of Components

V1 components without V3 equivalents

1. Back to top: Currently using v1, which is the most up to date component

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

1. Pagination
   • We are not using a component need to update to v3 component

Probably will be resolved with the Resources Landing page ticket but if not:

1. Breadcrumbs
   • Not using any component but should be using v3
2. Search input
   • We should be using the v3
3. Radio buttons
   • There might be some technical limitations here, I'm not sure but if possible we should be using v3 components

Documentation

Sitewide V3 DS component review spreadsheet

User story

AS A PO/PM for the PW team products, as well as for the Design team
I WANT all V1 components to be upgraded to V3 either before or soon after February 16, 2024
SO THAT all PW products are in alignment with the new components.

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

• V3 components are now used for the features listed above, and display/function correctly
• other features display correctly
• verify/review the E2E tests
• check desktop and mobile

[laflannery]

Adding Randi's notes from a previous ticket regarding the Pagination so when the element is updated to the component we don't lost these:

• Several templates in content-build utilize this pagination template:
• Need to explore whether we can add unit testing for this (is it possible in CB?)

[randimays]

Marking as a dupe of #17199 & #16986. This can be closed.

[FranECross]

Closing per note about duplicate above.