Visitar URL original
Workflow · uswds/uswds Wiki · GitHub
Skip to content

Workflow

Ryan Parker edited this page Sep 17, 2026 · 20 revisions

This page hopefully makes the USWDS workflow process more transparent. Check out the USWDS roadmap to see our current priorities. To get into detail, this view includes items from across the USWDS repositories.

Component Maturity Lifecycle

USWDS components and patterns have a defined maturity lifecycle that lives outside, but is related to, the workflow of issues and pull requests in GitHub. This maturity model describes how a component goes from concept to becoming an official USWDS component.

You can discuss ideas or approaches in this repo's Discussions: both officially in the Proposals section, and more casually in other areas. Community creations that may not be ready for evaluation to become part of the system but might be helpful to others can be posted and discussed in the Community Assets section.

USWDS currently depends heavily on its open source community's work. You can learn more on the main USWDS site and find out how you can contribute at USWDS's COMMUNITY.md and CONTRIBUTING.md.

Issues and Pull Requests

At a high level, here's the priority order for USWDS work.

When reviewing issues and pull requests submitted to USWDS:

Phase Description
Backlog
  • Add appropriate Labels:
  • Add Status
  • Add Type[s]
  • Add Skill[s]
  • Add Priority
In Progress
  • Add to a Milestone
  • Add assignee; whoever's working on a solution for this issue. This could easily be a contributor who has submitted a pull request that solves the issue.
  • Move to “In progress” status
Review/QA
  • Assign reviewer
  • Test on staging site
  • Code must pass all automated tests, manual checks and content reviews, and be a signed commit
  • Reviewer asks for changes and sends back to assignee, or approves
  • Reviewer changes Status to Initial Fed Review or Fed Final Review
  • GSA-internal federal staff completes final review and approval
  • Merge pull request, delete branch
  • Move to “Done”
Done Code has passed all automated tests, manual checks and content reviews, and has also been reviewed on staging for browser and device testing. Issue is closed.

For more information about our process, please read the contributing guidelines.

Clone this wiki locally