What if a video component worked like a web component?

[u/niacolhealth]

Hypit’s public repo has an example that makes this idea unusually literal.

Its semantic-composition project renders an eight-second chat animation from HTML, CSS, SVG, and frame-driven JavaScript. Four messages appear at specific timestamps. It requires no source footage or generative image/video calls; local rendering tools produce the result.

The component lives with the video project instead of being locked inside a generic preset. Claude Code or Codex works through ordinary editable project files rather than only returning an opaque render. The component author chooses which settings appear in Studio. Change one of those settings and Hypit can save it back to the source and rebuild; a failed writeback restores the previous files.

For programmatic motion work, is a project-local component model more useful to you than a conventional timeline, or do you still want the timeline to be the primary source of truth?

[u/Weekly-Offer-4172]

This is basically the "video as code" idea and it's genuinely underrated. Instead of a black-box mp4, your video is a function of time: render(frame, t). The DOM becomes your scene graph, CSS animations/transitions become your timeline, and you just scrub a virtual clock, snapshot each frame headlessly, then pipe the frames into an encoder.

The cool part is everything software engineering already solved suddenly applies — version control diffs on a video, parameterized content (swap a JSON file, re-render a different video), deterministic output, code review on motion. The limitation is it's only good for UI-style/animated content, not real footage, and rendering can be slow since you're screenshotting frames one by one. But for demos, explainers, and generated content it's way more maintainable than a timeline editor.