Build the open hardware index together
FCBase thrives on community contributions. Whether you maintain a manufacturer catalog, fly these boards every day, or just spotted outdated specs, your updates keep the database trustworthy for pilots, developers, and reviewers.
Before you submit
Follow these quick checks to help maintain data quality and speed up reviews.
Review the schemas inside /meta/schema/.
Always include reliable sources and update the verification block.
Run pnpm run validate before opening a pull request.
Ways to help
Contributions can cover any hardware covered by FCBase. Pick the area that matches your expertise and follow the structured schema fields outlined in the repository documentation.
Add new hardware
Submit flight controllers, transmitters, or component data backed by manufacturer documentation and reliable sources.
Improve metadata
Fix specs, add missing firmware support details, and expand sensor information to keep the database accurate.
Verify entries
Confirm data from hands-on experience, share validation photos, or flag inconsistencies that require review.
Contribution workflow
Use this checklist each time you contribute data. It keeps your updates consistent with the FCBase standards and helps reviewers merge changes faster.
Check existing data
Search the database first to avoid duplicates and note any fields that need clarification before you start editing.
Update the repository
Fork FCBase on GitHub, run pnpm install, and use pnpm run validate to ensure schema compliance before committing.
Open a pull request
Describe your changes, include supporting sources, and tag the PR using the feat(controller) or fix(data) prefix.
Need help?
Open a discussion on GitHub or tag maintainers in your pull request if you have questions about schema fields, vocabulary, or verification requirements. Clear commit messages and detailed PR descriptions speed up reviews for everyone.