The node reference is generated from metadata. Use it after you understand the file and surface model; do not rely on hand-maintained node lists for exact ports or params.

Registry facts

• The current generated registry contains 292 node descriptors.
• The registry is grouped into 20 categories.
• Each descriptor can include display name, category, context, description, inputs, outputs, parameters, defaults, dynamic port behavior, compound flag, use cases, and related nodes.

How to read a node page

• Confirm context first: DOM, Canvas, 3D, or shared.
• Read outputs before inputs so you know what the node produces.
• Read parameter defaults and enum options before authoring JSON.
• Check whether a port is dynamic or multi-input before wiring arrays or generated port names.

Category summary

• • inputs: 51 nodes
  • text: 31 nodes
  • animation: 28 nodes
  • boundary: 27 nodes
  • paths: 24 nodes
  • math: 17 nodes
  • solvers: 16 nodes
  • effects: 15 nodes
  • skeleton: 13 nodes
  • constraints: 11 nodes
  • integration: 10 nodes
  • distribution: 10 nodes
  • procedural: 9 nodes
  • state-machine: 8 nodes
  • falloff: 6 nodes
  • media: 5 nodes
  • bundles: 4 nodes
  • data: 3 nodes
  • attributes: 2 nodes
  • deformers: 2 nodes

Verified runnable examples

This guide points to proof-backed sample coverage. The full ledger lives in Generated examples and proof log.

DOM: Scroll fade reveal

• Source: faster-motion/demo/tests/dom/catalog/scroll-animations/fade-reveal/fade-reveal.domgraph.fmtion
• Expected output: Sections fade and translate into place as their trigger elements enter the configured viewport range.
• Validation: Schema validation passed. Runtime proof reports zero structural/runtime issues and 17 loaded nodes.
• Desktop proof: generated-assets/faster-motion-docs/proofs/screenshots/dom-fade-reveal-desktop.png
• Mobile proof: generated-assets/faster-motion-docs/proofs/screenshots/dom-fade-reveal-mobile.png

Canvas: Fill rule diagnostic

• Source: faster-motion/demo/tests/canvas/fillrule-diagnostic/fillrule-diagnostic.fmtion
• Expected output: A contained Canvas scene renders paired path cases so nonzero and evenodd fill handling can be compared visually.
• Validation: Schema validation passed. Runtime proof reports zero blocking runtime issues and 10 rendered objects; the accepted metadata note is preserved in the proof ledger.
• Desktop proof: generated-assets/faster-motion-docs/proofs/screenshots/canvas-fillrule-diagnostic-desktop.png
• Mobile proof: generated-assets/faster-motion-docs/proofs/screenshots/canvas-fillrule-diagnostic-mobile.png

Guide-specific sample target: Generated node page sample that renders one descriptor as a compact public reference table.

Faster Motion docs

Use this local map together with the left navigation. The source-backed content tree controls the main article order; this section keeps related pages one click away.

Start

• Faster Motion docs map
• Faster Motion documentation overview
• Get started with Faster Motion
• Faster Motion concepts
• .fmtion file format

DOM animation

• DOM animation guide
• DOM selectors and targets
• Scroll animation
• Pointer, hover, and drag inputs
• Text, SVG, and path animation
• Responsive gates and parameter overrides

Canvas animation

• Canvas animation guide
• Canvas area lifecycle
• Canvas objects, assets, and rendering
• Canvas inputs and state machines

3D and procedural

• Canvas 3D and procedural guide
• 3D scenes, cameras, and lights
• Procedural geometry and fields
• Particles and physics

Reference

• Node reference index
• Node categories reference
• Runtime loading and publishing
• Runtime API reference
• Debugging and preflight
• Debug API reference
• Validation errors and warning codes
• Faster Motion production checklist
• Faster Motion recipes overview