CreatorMotion · Column Annotations

Prepare three columns with title, image and short notes arrays. Give focusOrder valid integer indexes in the order you intend to discuss them. Include each column whose annotations should appear; omitted columns do not receive an animation pass.

Replace quick, considered and complete or use your own mapped keys. The helper accepts an exact key or its extension-free form, so content such as quick.png can use the quick image-map key. Although the guide calls image optional, the implementation calls requiredImage for every column; provide a resolvable image key.

Keep annotation counts within the available column height and per-column timing. Multiple notes reveal at 0.6-second spacing; long lists can overlap the next pass or the final reading state. No presenter video or alpha matte is used.

Prepare Node.js 22+, FFmpeg and the documented HyperFrames CLI 0.8.30. From the extracted package run node scripts/create.mjs --out PROJECT --data CONTENT.json with the chosen --style. Use semantic --overrides if needed. An --images JSON maps named slots to local files, with relative paths resolved beside the map and unlisted slots retaining bundled defaults. Read the image policy before replacing material.

Lint, validate and inspect the generated HyperFrames project, then render at 1920×1080 and 30 fps with the pinned CLI. Review real MP4 frames at the opening, each handoff and final state for clipping, contrast and correct labels. Keep at least 1.2 seconds for final reading when editing timing, and compare all palettes with identical content after module changes. Narration, music and film assembly remain separate work. Check the document/annotation match, each focus pass and restoration of all pages. Ensure dimming does not reduce annotation readability, and that your notes do not cover the very details they describe.