Motion Menu — the design system behind every Nimos build
What it is
Motion Menu is a numbered library of 597 working motion and design patterns — real HTML, CSS, and JavaScript, not screenshots or abstractions. It lives at motionmenu.ca, and it is not a client project in the usual sense. It is the design system Nimos Websites builds from. When you hire Nimos, your site inherits it.
What we built
A real site with live pattern demos: every pattern runs in the browser, on the page, so you judge it by how it moves rather than how it is described. The library is organised by role — hero, navigation, pricing, footer, background — and by technique, including scroll-driven work, WebGL, and seam transitions between sections. Patterns carry permanent numbers and slugs, so a build can reference "pattern 84" and get the same code every time.
Two agent-facing surfaces make it readable by software. A shadcn-compatible registry output means patterns drop into component-based projects without hand-porting. And `/p/<n>.md` endpoints serve each pattern's code as plain markdown, which is how the Nimos agents read it mid-build. The library was written to be used by software as much as by people.
The engineering
The patterns are self-contained: HTML, CSS, and JS with no framework lock-in, plus wrappers for React, Vue, and Svelte when a project calls for components. The registry is generated from the same source as the demos, so there is one truth, not a demo that drifts from the docs. Static delivery keeps the whole thing fast and cheap to run. Every pattern is numbered and versioned, so a quality check can name exactly what shipped.
What the business gets
Consistency and speed. Most agencies start each project from a blank file and charge you for the blank file. Nimos starts from 597 tested patterns, which is a large part of how a complete site ships in 3–5 weeks, not quarters. Your build gets motion and interaction design that would otherwise be a separate engagement with a specialist studio — scroll work, section seams, live backgrounds — because the patterns are already written, tested, and proven in a browser.
It also means your site is not a one-off nobody can maintain. The patterns are documented, numbered, and publicly inspectable at motionmenu.ca. Another developer can pick up your site and see exactly what it is built from.
Start yours
The same four steps build and maintain this library; a human checks the work. Clients own their sites forever — and every one of those sites is built on 597 patterns that are already working.