Four zones
Infeed, process step, inline quality control, and outfeed, divided at the same x positions the coating and calendering diagrams use.
Chapter 1 toolkit · Authoring tool
Lay out a machine diagram, then hand back the numbers.
The Chapter 1 production simulator draws each machine from fixed coordinates, so a label that overlaps at one screen width overlaps for every reader. This editor opens those diagrams, lets you move, rename, and resize any part directly on the canvas, and exports only what changed. It teaches nothing on its own — it is the tool the lessons are built with.
How it works
Four steps, then paste the result.
Everything stays in the browser. A draft is kept in this browser's local storage, and nothing is uploaded.
- 01
Pick a diagram. Coating and calendering are the two machines Part 03 draws. The standard template is an empty line to build a new one from.
- 02
Select a part. Click any label or machine on the canvas. Drag it, nudge it with the arrow keys, rewrite its text, or resize it.
- 03
Watch the collision count. It rechecks after every change, and marks any two labels whose boxes overlap.
- 04
Export. Copy or download the changes as JSON — offsets, scales, and rewritten text only, keyed by part.
Editor
Three diagrams, one canvas.
Each diagram keeps its own edits and its own history while you switch between them. “Reset this diagram” restores only the one on screen.
Diagram
Selected part
Nudge
Arrow keys nudge by 1, Shift + arrow by 5.
History
Ready to copy
Standard template
A blank line, already in the house style.
The third diagram is not a machine. It is the skeleton every CellForge machine shares, so a new process step starts from the same grid, the same zones, and the same label scale as the two that exist.
One web line
A single material path at y = 214 with flow arrows, so the input reel, the process head, and the output reel already line up.
Placeholder machines
A feed unit, a process head, a drive roll, an inspection camera, and an inline gauge — each one renameable into the machine the step actually needs.
State badges
Input, in-process, and output state badges along the bottom, so the material's condition is named at each stage rather than inferred.
Where the output goes
Changes belong in the module source.
The exported JSON records only offsets, scales, and rewritten labels, keyed by part. Apply it to the coordinates in the Part 03 payload, then re-run the module's static tests so the change is checked the same way the rest of the course is.
Back to the Chapter 1 study guide