ııı motion.mdVideo style specification
Notion / V303

Notion as code — workspaces in TypeScript

Move from a terminal requirement to a usable workspace. Code is an intermediate output; viewers must ultimately see the actual page it generates.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 51.07 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>Notion as code — workspaces in TypeScript · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#ffffff}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 elementsTerminal windowPromptPlan checklistCodeDeployment commandWorkspace
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Enter the goal before showing execution

Enter the goal before showing executionRule example
0.00 / 26.00 seconds
4–30 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>Notion as code — workspaces in TypeScript · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#ffffff}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="4" data-end="30"><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>

After the launch heading, enter the terminal and use a concise requirement to explain what to create. Reveal text at a typing pace, then expand the plan and constraints; execution logs must not precede the requirement.

02

Follow code with deployment and the workspace

Give an explicit deployment confirmation after code output, then cut to the light workspace result. Match the workspace title and structure to the initial request, turning black-background commands into an immediately understandable outcome.

03

Black and white work surfaces convey stage changes

Use a dark background and monospace text for the terminal, and white backgrounds with a sans-serif interface for results. Use medium-bold sans-serif headings and restrained pale outer backgrounds; the pointer, log highlights and completion state share one accent color.

04

Rewrite around one visible result

When changing the generation target, replace the prompt, plan, key code and final page together. Keep only enough code footage to explain the structure, reserving video time for the result showcase.

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 4.00 seconds
4.00s
Composition reference at 23.00 seconds
23.00s
Composition reference at 30.00 seconds
30.00s
Composition reference at 40.00 seconds
40.00s
Composition reference at 48.00 seconds
48.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace the generation target; preserve command → generation → deployment → visible result.

Production constraints

Terminal window / Prompt / Plan checklist / Code / Deployment command / Workspace

  • Enter the requirement before showing execution and code, then switch to the actual workspace result after deployment confirmation.
  • The black terminal and white result backgrounds distinguish stages.