ııı motion.mdVideo style specification
Perplexity / V256

Perplexity Projects — hubs for ongoing work

All files, tasks, and conversations belong to one project. Use containment and return relationships to portray a space for ongoing work.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 64.03 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>Perplexity Projects — hubs for ongoing work · 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>
Visual elementsParent project containerFileTask rowShared input fieldTeam messageResult
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

The project parents all content

Establish location with the project heading, then bring files and tasks into that scope. Retain at least its heading, boundary, or navigation; child items remain attached to the project while moving.

02

From incoming materials to project questions

Add files first, create tasks next, then ask within the project. Preserve file context across task changes; answers must not jump into an apparently new empty space.

OperationRelationships to preserve
Files flow inFiles belong to the current project
Parallel tasksTasks reference the same materials
Project questionKeep input and answers within project scope
Team messageReturn to the corresponding project and outputs
03

Use the overview to bring branches together

50.00s · Composition reference

Return to the project overview after team messages so files, tasks, and results are visible again. Use wider overview framing and local close-ups for details, making expansion and contraction express ownership.

04

Keep project boundaries lighter than content

Use pale warm color, teal selection, and dark type for hierarchy. Set project propositions in serif and file/task labels in sans serif; keep borders and links lightweight instead of turning the workspace into a dense flowchart.

05

Define the project before replacing content

Adapt to design sprints, research topics, or product launches. Define the project name and shared goal before adding files, members, and tasks; all must fit coherently in one overview.

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 11.00 seconds
11.00s
Composition reference at 23.00 seconds
23.00s
Composition reference at 39.00 seconds
39.00s
Composition reference at 50.00 seconds
50.00s
Composition reference at 61.00 seconds
61.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Retain the project as parent when adapting; replace files, members, and tasks without losing ownership.

Production constraints

Parent project container / file / task row / shared input field / team message / outputs

  • Files and multiple tasks belong to the same project rather than appearing as unrelated floating cards.
  • Move from in-project questions to team messages and back to overview to demonstrate persistent context.