Contributing

Thank you for considering contributing to FTCSoftware.org!

FTCSoftware.org is a community driven project, and we rely on the work of volunteer contributors to write and maintain articles.

Currently, the project is in a very early stage, where the initial content for the website is still being written. This also includes significant discussion on the structure, philosophy, and roadmap of the website, which is all actively in development. As such, this is a great time to get involved with the project. The current focus is on getting stages 0, 1, and 2 complete and setting up the website and our processes for long-term success.

This is a great time to get involved with this project and have an impact.

Where to contribute

FTCSoftware.org is a fork of FRCSoftware.org. Starting with the 2027-2028 season, FTC and FRC share a control system, so a lot of the tooling and much of the writing about it applies equally to both programs.

Before opening a pull request here, consider which repository your change belongs in:

• Contribute upstream to frcsoftware/frcsoftware.org for anything that isn’t specific to FTC. This covers site tooling, build and lint configuration, components, and content that would read the same on either site, such as Java fundamentals, general WPILib concepts, and command-based programming. Changes made upstream reach both audiences, and we pull them in from there.
• Contribute here for anything FTC-specific. This covers FTC examples and templates, FTC hardware and electronics, FTC game and field references, and any place where the FTC guidance genuinely differs from FRC.

If you aren’t sure which side a change falls on, open an issue or ask in the Discord and we’ll help you figure it out. Don’t let this stop you from contributing. Sending it to the wrong repository is easy to redirect, and we’d rather have the contribution than not.

Join our development Discord