Where does each instruction go?
| You want to change... | Put it in... |
|---|---|
| What every chapter must contain or structurally include (e.g. "always include a hands-on experiment") | Structure / example template |
| Who the tutorial is for and what it covers, factually | General content framing |
| The voice/tone for a delivered arrangement (e.g. "playful, for 10-year-olds") | Arrangement framing |
| A standing rule that must hold everywhere, no exceptions (e.g. "always respond in German") | System instruction |
Full explanation with worked examples: see the Guide page.
Project
Each project is a separate database — its own chapters, arrangements, and settings. Switch to work on a different tutorial, or start a new one from scratch. Switching affects the whole app immediately (there's no per-browser separation).
+ New project
Copies framing, system instruction, structure/example template, and example chapters into the new project. Chapters, arrangements, and content are never copied.
Model
Pick which LLM provider and model this project uses. Leave provider on
"Use config.json default" to inherit the deployment-wide setting; leave a model field
blank to use that provider's config.json/environment default instead of a specific one.
API keys stay in config.json only — never entered here.
This caps how long a single generated response can be — not the model's total context window (that's fixed by whichever model you pick). If a long chapter with several quiz sections keeps getting cut off mid-generation, raise this.
General content framing
Used by Draft and Refine on the Write page — nowhere else. Factual context only: who this is for and what the tutorial covers. No tone/style here — content stays neutral so it can be adapted differently per arrangement later.
Example: "A tutorial for 5th-grade children learning electronics using a robot kit called RobertOne. The kit includes: wooden base, 2 TT motors with wheels, ESP32-S3 microcontroller, DRV8833 motor driver, L7805 voltage regulator, ultrasonic sensor, breadboard, assorted components."
Arrangement framing (style & tonality)
Used by transitions and "Adapt to arrangement" on the Bridge page — never by Draft/Refine on the Write page. This is tone only. Adaptation is explicitly told to preserve structure and facts exactly and change only wording — so structural requirements placed here (e.g. "add an experiment section") will be ignored, not applied.
Example: "Write in a relaxed, motivating, engaging tone suitable for 5th graders, so the topics are easy to understand and fun to learn and experiment with."
System instruction
Used by everything — Draft, Refine, transitions, and adaptation alike. The one place for a rule with zero exceptions, like a fixed output language. Leave it as the default unless you need to change how the model behaves at a fundamental level.
Structure / example template
Used by Draft and Refine on the Write page, alongside General content framing. This is the right place for anything every chapter must structurally include — sections, a required exercise, a recurring narrative element — since it's the only field content generation actually reads for that kind of requirement.
Example: "Invent a breadboard experiment for each topic and include it as its own 'Experiment' section. Reference RobertOne throughout, so the robot evolves/gains new capabilities as the chapters progress. Do not write an introduction or a transition to the next chapter — those are generated separately."
Example chapters
Upload or paste one or more full chapters you're happy with — the model uses them as structure/style/detail-level reference when drafting on the Write page (not for their specific facts or topics). Used for every chapter for now (a per-chapter set is planned for later).