Good first contributions

Concrete ways to help without deep framework knowledge. Comment on an existing issue or open one describing what you plan to do.

Maintainers: label suitable issues good first issue or help wanted in GitHub.

Documentation

  • Fix broken links or version numbers (Studio 0.3.2, framework 1.2.0).

  • Add a short “how I debugged X” note to troubleshooting.

  • Improve glossary definitions from your onboarding experience.

Examples

  • Add a one-paragraph “what to look at in App.tsx” to an example README under examples/.

  • Verify examples/README matches workspace names in root package.json.

Tests and tooling

  • Extend a Vitest test in packages/react for a block you use in production.

  • Run npm run test:integration after CLI changes and document any new flags in CLI reference.

Studio (alpha)

  • Reproduce a Studio export bug with examples/studio-export and file an issue with project.json attached.

  • Align a Studio palette label with H5P capability map.

Before you start

  1. Read CONTRIBUTING.md and CODE_OF_CONDUCT.md.

  2. Use the smallest check matrix from the contributing guide (docs-only PRs do not need full e2e).

  3. Link your PR to the issue you picked up.