CreatorMotion · Document Collapse Contrast

Prepare two longPages keys, one shortResult key and two short labels in JSON. Use a source/result pair whose relationship you can explain accurately. The supplied example images demonstrate layout and do not prove a useful transformation.

Map raw-notes-1, raw-notes-2 and three-step-plan to your local images or use other valid keys. Filename suffixes can resolve to extension-free map keys. Every used key must resolve; the actual code does not fall back to editable document diagrams when a screenshot is missing.

Keep the two-source-page structure unless you adapt the code. Only the first two pages receive specific entrance animations, and fixed widths/camera movement assume that composition. The result fits a compact horizontal viewport; inspect its content rather than assuming a shorter box means a better answer. No presenter take or matte is required.

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 your chosen --style. Use --images for a local key-to-file map, with paths relative to that JSON and unlisted slots retaining defaults. Add semantic --overrides as needed and read the image policy before changing materials.

Lint, validate and inspect the generated HyperFrames project, then render at 1920×1080 and 30 fps using the pinned CLI. Review the actual opening, each change and final hold for text bounds, contrast, image fit and seams. Keep at least 1.2 seconds of final reading time when editing, and compare all palettes with identical content after module changes. Narration, music and film assembly remain separate work. Check source readability before contraction, the joint move and the result crop. Captions should describe the demonstrated difference without claiming an automatic summary or measured improvement that the assets do not show.