7 DOCS · READ IN ORDER
How it works.
Each claim tested.
Fizlet is the building blocks for animation and games on the DOM: a small kernel and bricks, so a piece boils down to logic and style. Start with the five-minute setup, then the ideas everything else rests on: the contract, the loop, Recall, the budgets and determinism. Every brick's API is in Bricks.
-
01 DOCS · GETTING STARTED
Getting started
Load Fizlet with one script tag or only the modules you need, start an engine, and give the page back with
destroy(). -
02 DOCS · AUTHORING
Authoring and recipes
How every Fizlet piece is written, the bricks to pick for each use, and three recipes that run on the page: an action, a shooter and two players.
-
03 DOCS · THE CONTRACT
The contract
The nine rules every brick and every game on Fizlet keeps, and the test that proves each one.
-
04 DOCS · THE LOOP
The loop
One shared requestAnimationFrame, a fixed 60 Hz step with a catch-up cap, three phases, auto-pause, settle and the fps cap.
-
05 DOCS · RECALL
Recall and the ledger
Every page change goes through one ledger: change-only writes, exact restore, and a newer host edit always wins.
-
06 DOCS · BUDGETS
Size budgets
Every module has a gzip budget checked in CI. The table is measured on the build you are reading.
-
07 DOCS · DETERMINISM
Determinism
A fixed step, a seeded random and state in typed arrays: runs replay, peers stay in lockstep, and syncCheck proves it.