I’ve always wondered why motion graphics still work so differently from the rest of the digital world.

We can build websites, apps, and even complex systems using structured files that are easy to edit and version-control. But for motion graphics, we still mostly rely on timelines, layers, and manually adjusting keyframes.

So I started building **Motionly** — an open-source motion graphics renderer that treats animations more like code.

The idea is simple:

Instead of thinking about an animation as a timeline, you describe the scene and let the renderer turn it into frames.

I want motion graphics to become:

* human-readable
* editable after creation
* reusable
* version-controlled
* easier to collaborate on

The bigger idea is also making motion graphics easier for AI agents to work with.

Because Motionly projects are stored as structured files, an LLM or coding agent can read, understand, and modify animations instead of generating a black-box video that cannot be changed.

The goal is not "AI video generation."

The goal is creating a common language between designers, developers, and AI — where motion can be described, edited, and rendered like software.

Right now, Motionly is still early, but the foundation is there:

* custom `.motion` file format
* parser + AST
* scene graph
* SVG/image rendering
* camera system
* animation presets
* preview renderer
* GIF/WebM export

I’m exploring where this could go next: product videos, UI demos, logo animations, launch videos, and creative coding.

I’d love feedback from people interested in:

* motion design
* creative coding
* graphics programming
* animation tools
* AI-assisted creative workflows

Does a "CSS for motion graphics" idea make sense?

Repo:  
[https://github.com/COPPSARY/Motionly](https://github.com/COPPSARY/Motionly)

What if making animations was like writing CSS instead of editing a timeline?