Skip to content

Contribute Without Code

github-actions[bot] edited this page Nov 6, 2026 · 3 revisions

Ways to help without code

You do not need to be a programmer to make OpenBridge better. This page lists every way to help that needs no code, how long each one takes, and the best place to start. It is for social workers, navigators, legal aid staff, policy researchers, translators, and accessibility testers.

OpenBridge is a prototype. All three states (Ohio, Texas, Washington) use draft rules that no expert has checked yet. Your help is what turns those drafts into rules people can trust.

The best first task

If you have one hour, record a test case. Pick a made-up household that looks like the families you see most often. Screen it in OpenBridge, say what result you expect for each program, and send us the file. Each test case is checked every time the rules change, so it keeps protecting families long after you send it.

Ways to help

Task About how long Good fit for How
Record a test case 30 to 60 minutes Caseworkers, navigators Record a test case
Report a rule that looks wrong 15 to 30 minutes Anyone who knows the program Report a rule problem
Review a state's rules as an expert Several hours per state Policy experts, agency staff, legal aid Review rules as an expert
Review the Spanish copy 1 to 3 hours Qualified Spanish translators Translate OpenBridge
Propose a new language 15 minutes to start Translators, community groups Translate OpenBridge
Test with a keyboard or screen reader 1 to 2 hours Accessibility testers, any user Test accessibility
Check or correct rules with the rule toolkit 30 minutes to a few hours Policy and legal experts Community rule toolkit
Ask for a new state, or offer to help 10 minutes Anyone Open a "New state request or offer" issue
Try it at your organization and tell us how it went Ongoing Navigators, program managers Guide for navigators

Times are rough guesses. Do as much or as little as you like. A single good report helps.

How to get started

Most help happens on GitHub, the website where OpenBridge's files and discussions live. An "issue" on GitHub is a public note that reports a problem or asks a question.

  1. Create a free GitHub account at github.com/signup. You only need an email address. You do not need to install anything.
  2. Go to the OpenBridge repository page and choose the Issues tab.
  3. Choose New issue. Pick the form that fits: "Eligibility rule correction", "Accessibility barrier", "Wording, docs, or translation", "New state request or offer", "Bug report", or "Feature request".
  4. Fill in the form and submit it. A maintainer will reply on the issue.

Prefer not to use GitHub? Email [email protected]. Say what you want to help with, and we will post your report or file for you and keep you updated.

Ground rules

  • Never share real people's details. Use made-up households with round numbers. This applies to issues, emails, test cases, and screenshots.
  • Cite official sources. A rule value should point to an agency page, policy manual, or published table. See Report a rule problem for what makes a good source.
  • Only experts verify. Anyone can report a problem, but only a subject-matter expert can mark a state's rules as checked. See Review rules as an expert.
  • Security or privacy problems go privately. Do not open a public issue. Follow the security policy.
  • Everyone follows the code of conduct.

What happens next

A maintainer reads every report and file. Rule changes are checked against the source you cite, and a subject-matter expert reviews them before a state can be marked verified. You can follow along on the issue and see what was changed.

Related pages

Clone this wiki locally