ııı motion.mdVideo style specification
Webflow / V352

A New Era of No-Code

Use a sphere as a visual guide through layered webpages, forms and workflow spaces. Interfaces are composable planes with depth rather than mere screenshots.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 103.53 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>A New Era of No-Code · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#100851}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsSphereWebpage planeWireframePortalFormConnection pathWindow group
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Layer webpages and pass the sphere between them

Layer webpages and pass the sphere between themRule example
0.00 / 9.00 seconds
4–13 seconds · Motion example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>A New Era of No-Code · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#100851}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="4" data-end="13"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>

Separate webpage backing, images, headings, and wireframes in depth. Move the small sphere along shared perspective, with near planes moving faster than distant ones.

02

Move from abstract space to concrete interfaces

Use portals and transparent cubes to change spaces, then establish workspace functionality through inputs, buttons, and controls. Keep blue-purple dominant, reserving pink, cyan, and yellow for local content.

03

Explain interface relationships through connections

Later, move data paths among windows, forms, and user nodes. Give paths clear origins and destinations, triggering the next window only after the sphere arrives.

04

Give the new subject a spatial guide too

Replace with product modules or business cards while retaining a recurring sphere or small guide. Prepare separable interface layers rather than using one screenshot for all depths.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 13.00 seconds
13.00s
Composition reference at 31.00 seconds
31.00s
Composition reference at 48.00 seconds
48.00s
Composition reference at 70.00 seconds
70.00s
Composition reference at 98.00 seconds
98.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace webpage content and business flow; retain sphere guidance, depth layers, and connections.

Production constraints

Sphere / webpage plane / wireframe / portal / form / connection path / window group

  • Separate webpage backing, images, headings, and wireframes in depth. Move the small sphere along shared perspective, with near planes moving faster than distant ones.
  • Use portals and transparent cubes to change spaces, then establish workspace functionality through inputs, buttons, and controls. Keep blue-purple dominant, reserving pink, cyan, and yellow for local content.
  • Later, move data paths among windows, forms, and user nodes. Give paths clear origins and destinations, triggering the next window only after the sphere arrives.
  • Replace with product modules or business cards while retaining a recurring sphere or small guide. Prepare separable interface layers rather than using one screenshot for all depths.