11. Where to Go Next

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 visible result at a time:

• Blink an LED for the smallest hardware proof
• Read a Button for digital input
• Read a Sensor for ADC and knob input
• Build a Calculator for a local, non-board state exercise
• Build a Small Game for the Machine loop

Tutorials are allowed to repeat a little. Their job is to get a working shape under your fingers.

If You Have A Froth Machine

Go to Machine . It teaches the workshop board as an object you can use:

• display
• joystick
• knobs
• simple drawing
• small game patterns

Then use Workshop for the puzzle-style activity and quick reference.

If You Need Exact Behavior

Use Reference when the wording has to be exact:

• Word reference for core syntax and language values
• Interactive profile for prompt behavior, interrupts, and inspection
• Image and persistence for save, restore, dangerous.wipe, and boot
• Hardware for board APIs
• CLI and Editor for tooling

The reference is not a tutorial. It is the place to check names, arity, availability, and recovery behavior.

If You Are Extending Froth

Read FFI and C next, then the FFI reference . Project FFI is the path for adding project-local C bindings. Board FFI is the path for firmware-owned board surfaces.

If You Are Coming From OldFroth

Read How Froth Is Different . The short version is that current Froth keeps the live image, coherent redefinition, recovery, and small-device discipline, but replaces the user-visible stack model with lexical values and named places.

Next: FFI and C if you want the extension boundary.