Add launch video and README demo - #59
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a-baran-orhan
marked this pull request as ready for review
July 14, 2026 20:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The README already had strong motion GIFs, but it did not show the complete prompt-to-Posecode-to-render workflow. The new demo gives developers an optional 28-second overview without adding another autoplaying visual to the page.
Impact
README visitors can click the payoff image or demo link to watch the builder overview. Maintainers can reproduce the horizontal, vertical, and still assets from the checked-in Remotion source.
Validation
npm test— 259 tests passednpm run typecheck— passedgit diff --check— passednpm run video:cut2:still— rendered the payoff still successfullyRemotion emits a dependency-detection advisory because the parser/MCP workspaces use Zod 3 while Remotion carries Zod 4 in its own dependency tree; the render completes successfully and the workspace dependency graph remains valid.