git.motiongit.com · Video source collaboration

Give video
a life beyond one edit.

Start with editable source. Fork a project, improve its animation, and build the next version together with its creators.

Discover and use templates in the template center. Read source and collaborate here.

~/orb-fusion-intro (softer-intro)Workflow illustration
Give every improvement its own branch · Refine the entrance timing · Compare source and discuss changes · Build a package from a pinned commit
Complete projectsGit historyForks & pull requestsPinned-commit buildsOpen .motion spec

01 / OPEN PROJECTS

Your first collaboration starts with a real project.

Approved public source projects from published templates. Repository activity is a locally synchronized summary.

Browse all source repositories →

Website templates have not opened source collaboration yet

Approved projects will appear here. You can also explore existing public source repositories.

Explore source repositories →

02 / FORK → IMPROVE → REVIEW

Improve templates together.

Keep the creator’s provenance, and give every improvement a clear path forward.

Fork Workflow illustration

motion.json
src/main.js
params.schema.json
assets/
licenses/
Start with the source

Source diffs and pull request review are available. Video diffs and frame-level review are interactive prototypes. Explore the video collaboration demo →

03 / BUILT ON .MOTION

Collaborate on the complete video project.

Git tracks changes. .motion describes the project. Code, assets, parameters and provenance travel together.

.motion / 0.1-draft ↗

Source you can read and edit

Change the content and choreography while keeping the project structure. Hand over more than a finished video.

src/ · assets/

An explicit parameter contract

Describe editable inputs and their constraints, giving people and AI a shared entry point.

params.schema.json

Builds with a clear origin

Build .motion from a pinned commit and record its origin. Source merges and marketplace releases are reviewed separately.

commit → build → release

Licensing and provenance included

Keep licenses and provenance with the project so reuse starts with a check of permissions and assets.

licenses/ · provenance

04 / SOURCE TO RELEASE

Ship an improvement as a reusable version.

Collaborate in the source site. Preview, review and distribute in the template center.

  1. 01

    Source commit

    Pinned commit

  2. 02

    Build project

    Generate .motion

  3. 03

    Checks & review

    Maintainer submits release

  4. 04

    Template center

    Preview · download · reuse

Merging a pull request does not update the marketplace template. New versions must pass checks and release review first.

CREATE THE NEXT VERSION

Start with your first fork.

Your account works across MotionGit. Find a project and start collaborating.

Start collaborating ↗