Generated schema reference

Updated Jun 21, 2026 3 min read

Product media placeholder

Replace this area with a screenshot or short walkthrough video during the media sweep.

This page is generated from the current Faster Motion JSON schema. Use it as a root-key map before opening the detailed guide pages.

Schema path faster-motion/dist/fmtion.schema.jsonRoot required keys metaDefinitions 204

Root keys

Key	Shape	Summary
`$vars`	declared	Root-level source key.
`assets`	declared	Root-level source key.
`canvas`	declared	Root-level source key.
`carousels`	declared	Root-level source key.
`customEases`	declared	Root-level source key.
`dataBindings`	declared	Root-level source key.
`dataTables`	declared	Root-level source key.
`dom`	declared	Legacy 2D scene array. Required in the original FmtionFile shape; marked optional during the F385 dev cycle so files in the new `scenes[]` shape validate against the same generated schema. Phase 7 (writer cut) deletes this field per the OQ-4 hard-cut decision (2026-05-15).
`domGraph`	declared	Root-level source key.
`domSpritesheetTracks`	declared	Root-level source key.
`enums`	declared	Root-level source key.
`fmtionVersion`	declared	Root-level source key.
`imageTrail`	declared	Root-level source key.
`inputs`	declared	Root-level source key.
`listeners`	declared	Root-level source key.
`meta`	declared	Root-level source key.
`parameters`	declared	Root-level source key.
`pointerFollow`	declared	Root-level source key.
`scenes`	declared	F385 unified scenes shape. Optional during the F385 dev cycle (Phases 1-6); Phase 7 (writer cut) makes this required and removes the legacy `canvas[]` / `3` fields above per the OQ-4 hard-cut decision (2026-05-15). Each scene declares its `kind: '2d' \| '3d'` and either lives in the DOM via `mountSelector` or renders headless via `output: { as: 'texture', ... }`. See `Scene.ts` and `faster-roadmap/animation/features/F385-unified-scenes-schema/`.
`smoothScroll`	declared	Root-level source key.
`videoTracks`	declared	Root-level source key.

Definition groups

The generated schema currently exposes 204 reusable definitions. The public reference keeps this page compact; detailed field-level examples belong on guide and example pages where the shape is easier to read.

Was this guide helpful?