Skip to content

Remove admonition definition from glossary; separate FTC vs FRC #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JediScoy merged 1 commit into from
May 11, 2026
Merged

Remove admonition definition from glossary; separate FTC vs FRC #48

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions docs/media/qr code - programmers handbook.svg
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 0 additions & 3 deletions docs/source/glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,6 @@ Terms used consistently throughout this handbook. When a word has multiple indus

## A

**admonition**
A styled callout block in the handbook (e.g., `!!! note "Coach"` or `??? info`). Used for coach notes, Current FTC sidebars, and warnings.

**AprilTag**
A fiducial marker used on FRC and FTC fields. Cameras detect them to estimate the robot's 3D position relative to a known tag location.

Expand Down
20 changes: 4 additions & 16 deletions docs/source/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,21 +5,7 @@

# **Introduction**

Welcome\! We hope these Guides will help you transition from FTC-style programming to FRC Command-Based programming. If you've done FTC, you already know more than you think — many concepts transfer directly, just with different names and patterns.

> **Publishing note:** These docs are built with **Material for MkDocs** and published via **GitHub Pages**.

## **FTC → FRC: Key Differences**

In 2026-2027, FTC uses an **iterative/time-based** Java approach where your `opModeLoop()` runs continuously and you check conditions each cycle. FRC's **Command-Based** framework is *event-driven* — you declare what should happen when certain conditions are met, and the framework handles the execution.

| FTC Concept | FRC Equivalent |
| :---- | :---- |
| `opModeLoop()` checking conditions | Triggers that automatically fire commands |
| Big `if/else` chains in teleop | Button bindings in RobotContainer |
| Motor/servo wrapper classes | Subsystems |
| State variables scattered around | State machines within subsystems |
| `LinearOpMode` | Command-Based Robot project |
Welcome\! We hope these guides originally started as a transition from FTC to FRC. We are currently revising them to help new programmers learn Java for FTC robotics and FRC robotics. There are numerous pages on WPI Lib to help you learn about programming for FIRST robotics. In our experience though new programmers don't know where to start and as of today does not seem to be a clear learning path for newbies. We hope to bridge the gap with our guides.

## **How to Use These Guides**

Expand All @@ -39,8 +25,10 @@ In 2026-2027, FTC uses an **iterative/time-based** Java approach where your `opM

## **Getting Help**

- **Stuck on a concept?** Ask in myself, teammates, email
- **Students stuck on a concept?** Ask myself, teammates, or email.
- **Code not working?** Check the WPILib docs first, then ask
- **Found a bug in these Guides?** Let us know so we can fix it\!

**Remember:** Every experienced programmer was once a beginner. The only bad question is the one you don't ask.

(https://bit.ly/frc3603-programming)
Loading
Loading