Skip to content

Tutorials

Each tutorial builds one thing from nothing and stops when it works. They are written to be followed in the app with the page open beside it, and every one says what landed on disk at each step — because a project is a folder, and knowing what is in the folder is most of knowing the app.

  • Your first story — a project, a board, three passages, a choice and the play button. Ten minutes.

Listed so you know they are coming, not as links, because nothing here should 404:

  • A dice roll that matters — a Dice roller, a Comparator and an If, so a climb can fail.
  • Six goblins — a component, a Spawn node, and a script that gives each one its own hit points.
  • A door with a state — a state machine file, the node that drives it, and a Switch on where it is.
  • The same story in two languages — adding a language, the staleness dot, and what the reader sees.
  • Handing it to a build — compiling a campaign, delivering the prose as HTML, and reading the bundle without the app.
  • An assistant in the folder — connecting Claude Code, and what to ask it first.

If one of these would help you now, say so in the support discussions — the order is decided by who asks.