The guide gives you the model. The next page depends on what you are trying to do.
If You Want A Task
Use Tutorials when you want one result at a time:
- Blink an LED for the smallest hardware proof
- Read a Button for digital input
- Read a Sensor for analog input
- Fade an LED when you are ready for PWM
- Build a Calculator for named state without more wiring
If You Need Exact Behavior
Use Reference when the wording has to be exact:
- Word reference for core syntax and values
- Interactive profile for prompt behavior, interrupts, and inspection
- Image and persistence
for
save,restore, and recovery - Hardware for ESP32-facing words
- CLI and Editor for tooling
If You Are Extending Frothy
Read FFI and C next, then the FFI reference . Native extensions are a build-time C path for the cases where Frothy code really needs a hardware or performance helper.
Design Differences
Read How Frothy Is Different for the deeper design notes: live image, coherent redefinition, recovery, small-device discipline, lexical values, and named places.