01 / Understand
Make it clearer.
Follow one guide. Fix an unclear instruction or broken link, and explain where you got stuck.
Build the next chapter
Careful questions and small improvements belong here, alongside code.
01 / Understand
Follow one guide. Fix an unclear instruction or broken link, and explain where you got stuck.
02 / Try
Check a page with a keyboard, a small screen or a screen reader. Report a specific barrier and a focused improvement.
03 / Build
Choose a bounded issue, reproduce a documented example with public fixtures, or review one research assumption.
Use central Discussions on GitHub for general questions and ideas across projects. Report actionable bugs in the repository that owns them. Issue labels help identify scope; they do not promise mentoring or immediate review.
Before changing code, read the contribution guide and code of conduct . Keep private data out of reports and use the documented disposable environment for network tests.
Independent verification, accessible documentation and relevant research all help. The supporting guide on GitHub explains current needs and verified contact routes. It currently publishes no live sponsorship or payment offer. No donation is required to contribute.