Product media placeholder
Replace this area with a screenshot or short walkthrough video during the media sweep.
Start by deciding whether the animation belongs to the page DOM or to a Canvas-rendered scene. The same .fmtion container can describe both, but the authoring model and verification checks are different.
Basic workflow
- Pick the surface: DOM, Canvas 2D, or Canvas 3D/procedural.
- Create or update the .fmtion file with metadata, parameters, inputs, and the relevant graph section.
- Load the file with the Faster Motion runtime in the page that owns the target DOM or Canvas mount.
- Run preflight and runtime validation before publishing.
- Verify the public page at desktop and mobile sizes, including reduced-motion behavior when relevant.
Minimal authoring shape
{
"meta": { "name": "Example motion" },
"parameters": {},
"dom": [],
"canvas": [],
"domGraph": {
"nodes": []
}
}
Start with one visible result
For the first version of a motion file, make one result easy to verify: a section fades in, a card follows pointer progress, a Canvas object moves, or a particle system renders in a known mount. Add complexity after that result passes validation.
Do not skip validation
- Use Debugging and preflight before treating a file as production-ready.
- Check that selectors match real DOM, ports exist, graph wires resolve, and the runtime can mount the target surface.
- When a page uses both DOM and Canvas, verify each surface independently before checking the combined visual.
Working sample slot
Getting-started sample: Insert a minimal .fmtion file and matching HTML mount once the example is verified. This page intentionally reserves the sample location so the live docs can ship before the verified examples are inserted.
Faster Motion docs
Use these pages as the first public Faster Motion documentation set. Working samples will be inserted after each sample is verified.
Start
- Faster Motion documentation overview
- Get started with Faster Motion
- Faster Motion concepts