mirror of
https://github.com/hanzoai/frames.git
synced 2026-09-24 00:08:03 +00:00
zooqueen
75094e0d60
@hanzo/frame is taken by the hero video primitive — one full-bleed video element — which has held that name on npm since it shipped. This repo is the video toolchain: a CLI, a renderer, a studio, a player. Plural is what it is, so the CLI publishes as @hanzo/frames and the workspace packages follow it (@hanzo/frames-core, @hanzo/frames-engine, and the rest). The binary stays `frames`, and now actually ships. The manifest mapped it to bin/frames.mjs while the file on disk was bin/hyperframes.mjs, so a global install produced no working command. The paths that name a package to fetch were pointing elsewhere. The update check read registry.npmjs.org/frames, a different author's package, and the npm, bun and pnpm installers would have pulled it over the CLI; the render image installed the upstream hyperframes; scaffolded projects and the docs pinned the unscoped name. All of them now name @hanzo/frames.
886 B
886 B
storyboard-sample (Studio fixture)
A small, self-contained project for dogfooding the Studio Storyboard view. Not a registry catalog item — it lives here purely as test content for the storyboard UI/UX work.
It exercises the storyboard contract end to end:
STORYBOARD.md— structured manifest (frontmatter + 5 frames) in the canonical format the parser reads.compositions/frames/0{1..4}-*.html— live HTML frame sub-compositions (built/animatedstatuses) the contact-sheet tiles render.- Frame 5 (
05-cta.html) is intentionally absent andstatus: outline, so the grid has an outline placeholder to render.
Preview the storyboard view:
npx @hanzo/frames preview packages/studio/fixtures/storyboard-sample
Inspect just the parsed manifest the Studio consumes:
curl localhost:<port>/api/projects/<id>/storyboard | jq