Perplexity — Portable Computer on NVIDIA DGX Spark
Use tasks to establish what the local device does, then architecture to explain connections to tools and cloud. Alternate concrete results with abstract relationships.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Perplexity — Portable Computer on NVIDIA DGX Spark · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fafaf7}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
Connect device and task first

Follow the device heading with local selection and task input. Retain a device or local marker on the pale warm canvas, using serif propositions and sans serif fields; teal marks execution focus and gray tool nodes remain secondary.
Arrange local tools around the device
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Perplexity — Portable Computer on NVIDIA DGX Spark · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fafaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="34" data-end="43"><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>Place tools, models, environments, and execution capabilities around the local node. Converge links on one center, leaving room for names; advance the current action along relevant links while other relationships stay calm.
Add cloud as a separate layer
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Perplexity — Portable Computer on NVIDIA DGX Spark · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fafaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="59" data-end="77"><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>Introduce cloud nodes outside the local network through one explicit connection. Resume local work after cloud review returns; do not mix cloud nodes into the local tool ring.
Interleave three tasks with two architecture explanations
Use the first task to establish the product, the second to explain cloud collaboration, and the third for team results. Follow every architecture segment with a concrete output to ground topology in work.
Preserve local-cloud roles when adapting
Replace devices, tools, and business tasks. Define every node's responsibility before choosing local actions and external collaboration; use consistent names between results and execution nodes.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Replace devices and tools while preserving local execution and on-demand cloud-collaboration boundaries.
Production constraints
Local device / tool ring / cloud model / task box / report / team message
- Arrange local tools in a ring around the device, with cloud models on a separate layer; connectors indicate escalation when needed rather than default data transmission.
- Interleave task examples with architecture diagrams rather than showing only abstract topology.