ııı motion.mdVideo style specification
Miro / V351

Miro | Product launch collection

Carry one product project through goals, research, design and development. Preserve its name or key question at every view change so the long video reads as one advancing workflow.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 144.13 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>Miro|Product launch collection · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfaf7}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 elementsSticky noteCollaborator cursorGoal tableTimelineInsight cardPhone prototypeDocumentArchitecture diagram
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Gather the team's problems first

Cut from yellow branding to a pale canvas, adding business-goal cards and named cursors progressively. Center the main question with surrounding notes responding; do not fill the frame with goals, research, and prototypes together.

02

Turn goals into schedulable work

Turn goals into schedulable workRule example
0.00 / 6.00 seconds
53–59 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>Miro|Product launch collection · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="53" data-end="59"><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>

Pass through goal tables, milestone timelines, and boards. Match project colors between table rows and Gantt bars, with the right assistant panel explaining only the current step.

03

Let user insights actually shape the prototype

Let user insights actually shape the prototypeRule example
0.00 / 8.00 seconds
93–101 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>Miro|Product launch collection · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="93" data-end="101"><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>

Organize feedback into insight cards, open generation from a card, then show the phone prototype. Sequence question, action choice, and result; do not substitute an unrelated phone page.

04

Hand design to development at the end

Show product descriptions, entity diagrams, phone interfaces, and code workspaces in turn. Retain a small thumbnail or shared heading from each preceding step, using the overall timeline to explain strategy through delivery.

05

Replace upstream and downstream content with the project

Prepare business goals, three insights, one prototype, and development notes for one theme. Use note colors only for grouping; keep phones and documents white with dark text, using purple, blue, and pink as secondary colors without a new primary.

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 19.00 seconds
19.00s
Composition reference at 43.00 seconds
43.00s
Composition reference at 84.00 seconds
84.00s
Composition reference at 110.00 seconds
110.00s
Composition reference at 133.00 seconds
133.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace the complete project and collaborators, preserving goal→research→prototype→architecture→delivery.

Production constraints

Sticky note / collaborator cursor / goal table / timeline / insight card / phone prototype / document / architecture diagram

  • Cut from yellow branding to a pale canvas, adding business-goal cards and named cursors progressively. Center the main question with surrounding notes responding; do not fill the frame with goals, research, and prototypes together.
  • Pass through goal tables, milestone timelines, and boards. Match project colors between table rows and Gantt bars, with the right assistant panel explaining only the current step.
  • Organize feedback into insight cards, open generation from a card, then show the phone prototype. Sequence question, action choice, and result; do not substitute an unrelated phone page.
  • Show product descriptions, entity diagrams, phone interfaces, and code workspaces in turn. Retain a small thumbnail or shared heading from each preceding step, using the overall timeline to explain strategy through delivery.
  • Prepare business goals, three insights, one prototype, and development notes for one theme. Use note colors only for grouping; keep phones and documents white with dark text, using purple, blue, and pink as secondary colors without a new primary.