Typography · Rendered draft
Dock · staggered assembly, pair removals and surviving icon
Study the source, inspect the editable build, then adapt the treatment to your own content.
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
A runnable draft is not a fidelity approval.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- The84-file source kit contains28 original SVG assets/controls and exact1386-row Resolve layer states; two99-frame replays are provided separately. The33 Node tests,10 gate groups and6 archive-test groups pass; typecheck is clean and both frozen outputs pass unchanged-core verification. The selected runtime needs three pinned companion archives, supplied separately here. SVG Gaussian-shadow controls are approximations, not the measured CSS-preparation route. Native Resolve, moving-quality review and source wins remain unverified. The native-source archive supplies56/99 positions and leaves43 gaps; no upscaling or smaller-movie decoding is counted as restoring them. The frozen source comparison now ties both variants after396 static movie-frame instances. Native crops cover42 positions per candidate and56 shared source positions. Exit readability at73→74 remains unassessed in motion, not a confirmed fault.
- The existing package is retained unchanged. Local checks verify its bytes, archive, media, and route; no new fidelity approval is asserted.