Read the project's contributor guidelines
- copyedit documentation
- localization
- accessibility
- alt text (example alt text PR)
- tool testing: screen reader, keyboard nav
- test/validate issues, PRs, and examples
- esp. old issues - can they be closed?
- "good first issue"s
- first check: is anyone actively working on it?
- If you find a problem with the repo's setup documentation, fix it or raise an issue!
- Be sure to build/run/test main before making changes
Stuck? Ask questions on the issue, at a community call, on discourse.
It is very typical for any PR, especially from a first time contributor, to need a few rounds of feedback+revision before merging.