Computer launches Automations
Explain automation through two clear stories: one triggered by an external event and another by a schedule, each covering conditions, execution, and results.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Computer launches Automations · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#071128}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>Motion and composition
Local motion · Composition rules
Arrange two trigger paths first
Use the first half for event notifications and the second for recurring tasks. Reset attention with a short middle heading, reusing interface positions so viewers understand the difference as a change in trigger.
Let the event actually drive later actions
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Computer launches Automations · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#071128}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="6" data-end="31"><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>Show condition settings before creating automation; start the execution list only after the notification appears. Use the pointer to clarify clicks and notifications and task states to explain causality.
Advance execution rows by dependency
Keep tasks to three to five rows. Accent the current row and settle completed rows into a stable state; introduce the result panel after the last required step, not alongside the initial loading state.
Emphasize time in recurring tasks
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Computer launches Automations · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#071128}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="48" data-end="81"><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>In the second example, show frequency, trigger time, and output in order. Hold the time node for independent reading and accelerate execution if needed; compress repeated settings while fully explaining the new trigger logic.
Support both workflows with a deep blue canvas
Layer brighter work panels over a large deep blue background. Use serif proposition headings and sans serif settings and task states; focus on one action area at a time, shifting fine lines and glowing edges with it.
Change trigger, work, and delivery together
Replace events, task steps, and output as one business scenario. Keep input within three lines; if demonstrating only one trigger type, retain one complete example and proceed directly to the brand close.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Replace trigger events, frequency, and outputs; preserve both trigger patterns.
- Keep long input copy within three lines and execution steps to three to five items.
Production constraints
Trigger condition / task list / notification bar / time node / output card
- Separate event triggers and scheduled triggers into two complete examples, each with condition → execution → output.
- Activate task-chain rows in sequence, with results after processing; interleave abstract headings with action evidence.