Verification plan for remaining components

[natalia-fitzgerald]

The purpose of this issue is to establish the verification plan for components moving forward. This issue will also establish the plan for components that are not in the DS. We should probably establish a separate verification process for these components that does not include the DS step.

DSR groupings

Verified

Component exists in Design System and Design System in React (and the two are aligned)

CF.gov (unverified)

In cf.gov but not in Design System

Other

Components that are not in the Design System, no consistent style has been previously defined, and component does not exist (at least consistently) on cf.gov

Draft

Any components that are in progress (includes verified, cf.gov, and other)



Components organized by DSR groupings

This is meant to show where components will live in a future state. I added the “Pending verification grouping for the sake of tracking the current work)


Verified


• Banner (US gov)

• Buttons

• Checkboxes
• Working on enhancement to DS style

• Headings

• Labels

• Links

• Pagination

• Paragraphs

• Radio Buttons

• Tables

• Taglines

• Text introductions

• Text inputs
• Wells



Pending verification

• Alerts: Is it blocked by enhancement to DS style? https://cfpb.github.io/design-system/components/alerts

• Heroes: https://cfpb.github.io/design-system/patterns/heroes

• Lists: https://cfpb.github.io/design-system/components/lists

• Icons: https://cfpb.github.io/design-system/foundation/iconography

• Dropdowns (should be called Selects): https://cfpb.github.io/design-system/components/selects

• Main content and sidebars: https://cfpb.github.io/design-system/development/main-content-and-sidebars
- Helper text: https://cfpb.github.io/design-system/components/helper-text

• Grid: https://cfpb.github.io/design-system/foundation/grid


CF.gov (unverified)

• Breadcrumb

• Navbar (Should be called Navigation or Page-level navigation)

• Page header (should be called cf.gov header or Header or something else)

• Divider

• Footer


Other


• Step indicator: This does not exist in cf.gov. I have mock-ups that we can review/compare/discuss. 

• File upload (This does exist in cf.gov but component is not consistent. First step would be a component audit - which I’ve done. Then perhaps we can discuss the options?)

• Progress indicator: As far as I know this does not exist in cf.gov. I have some mock-ups that we can review/compare/discuss. 


Draft

Groupings for tasking


1. Current sprint (in progress)


• Alerts: Is it blocked by enhancement to DS style?

• Text inputs: Complete 1/30/2024
• Checkboxes - Complete 1/30/2024

2. Backlog (needed for app pages)


• Heroes

• Lists

• Icons

• Footers

• Navbar

• Page header

• Dropdowns
• Divider
 

• Grid?

• Layout?
• Expandable*


3. External dependencies


• Expandable (Virginia)

4. Deprioritized



Questions:

Why do we use folders for some components?

• Should we change the name of the page header component to “cf.gov header or something else?
• Can we merge the most updated changes to Dropdowns even if we leave this component in Draft?
• Should we change the name of “Navbar” to “Navigation”?
• Do we want to add the “Fieldsets” component: https://cfpb.github.io/design-system/components/fieldsets
- Do we want to include any of this? 

• Do we want to include any of this? 
  

[billhimmelsbach]

I think we can put this in the backlog for now? We can revisit verifying more components in later sprints?