Contribute on GitHub — Help Charities With a Pull Request

Everything Free For Charity builds is open source. If you can open a pull request, you can help a nonprofit today — no application form, no meeting, no minimum commitment. Sustained contributors naturally grow into named volunteer roles (with training and sponsored certifications), but the door in is just… a PR.

Where to contribute

• FFC-IN-freeforcharity.org — This website — content, components, accessibility, tests. The friendliest place to start.
• FFC-IN-FFC_Single_Page_Template — The template every new charity site starts from — improvements here reach every future charity.
• FFC-IN-Footer_Only_Template — The minimal template (team + footer) for charities that just need a presence.
• FFC-Cloudflare-Automation — Infrastructure automation: DNS, metrics pipelines, operational workflows (PowerShell + GitHub Actions).

Finding a first task

Issues labeled good first issueare scoped, self-contained, and reviewed kindly. Comment “I’ll take this” on the issue before you start so nobody duplicates your work.

The house rules (reviewers will check these)

• Conventional Commits: feat:, fix:, docs:, test:, chore: prefixes on commit messages.
• Branch + PR, never direct to main.Link your PR to its issue (“Fixes #123”).
• kebab-case for all web folder names (SEO + screen-reader friendly).
• Accessibility is enforced— jest-axe and WCAG scans run in CI, and PRs that fail them don’t merge.
• Run the checks locallybefore pushing: lint, unit tests, build (each repo’s README lists the commands).

Why this matters

A fix to a shared template ships to every charity built from it; a clearer guide page deflects dozens of support conversations. Small PRs here have unusually large blast radius — that’s the fun of it. See the impact page for what the volunteer engine has produced so far.

Ready for more than drive-by PRs? The volunteer onboarding guide shows what your first two weeks as a regular look like.