# 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.
```motion-demo
{
"id": "sequence",
"title": "Overall choreography",
"src": "demos/sequence.html",
"duration": 64.033333,
"status": "authored",
"description": "Motion and composition example",
"initialTime": 11,
"params": [
{
"key": "title",
"label": "Sample main copy",
"type": "text",
"value": "Projects in Computer",
"maxLength": 60
},
{
"key": "accent",
"label": "Accent color",
"type": "color",
"value": "#2c8587"
}
],
"presets": [
{
"label": "Default content",
"values": {
"title": "Projects in Computer",
"accent": "#2c8587"
}
},
{
"label": "OpenDesign adaptation",
"values": {
"title": "OpenDesign",
"accent": "#7050da"
}
}
]
}
```
## 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.
## 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.
| Operation | Relationships to preserve |
| --- | --- |
| Files flow in | Files belong to the current project |
| Parallel tasks | Tasks reference the same materials |
| Project question | Keep input and answers within project scope |
| Team message | Return to the corresponding project and outputs |
## Use the overview to bring branches together
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.

## 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.
## 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.
## Color and typography
Serif proposition headings with sans serif interface text; generous whitespace and fine borders.
#fafaf7 · #171917 · #2c8587 · #dbe4df · #ffffff
## Elements and production rules
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.
## Content replacement
- Retain the project as parent when adapting; replace files, members, and tasks without losing ownership.
## Production parameters
[Visuals and objects](style.json) · [Section timing](timeline.json) · [Position data](tracks.json) · [File manifest](manifest.json)
This specification is based on the reference video. The HTML provides editable choreography examples; each file identifies the source, precision and valid interval of its data.
```motion-board
{
"version": 1,
"brand": "Perplexity",
"id": "V256",
"palette": [
"#fafaf7",
"#171917",
"#2c8587",
"#dbe4df",
"#ffffff"
],
"typography": "Serif message headings with sans-serif interface text, ample negative space and thin borders",
"sample": "Projects in Computer",
"objects": [
"Parent project container",
"File",
"Task row",
"Shared input field",
"Team message",
"Result"
],
"frames": [
{
"path": "assets/reference-1.jpg",
"timeSeconds": 0.0,
"frameId": "K0001",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-2.jpg",
"timeSeconds": 11.0,
"frameId": "K0026",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-3.jpg",
"timeSeconds": 23.0,
"frameId": "K0050",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-4.jpg",
"timeSeconds": 39.0,
"frameId": "K0090",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-5.jpg",
"timeSeconds": 50.0,
"frameId": "K0106",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-6.jpg",
"timeSeconds": 61.0,
"frameId": "K0136",
"role": "reference-evidence",
"status": "measured"
}
],
"stages": [
{
"start": 0,
"label": "Project heading",
"end": 6,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 6,
"label": "Files flow in",
"end": 11,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 11,
"label": "Parallel tasks",
"end": 18,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 18,
"label": "Unified-context proposition",
"end": 23,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 23,
"label": "Ask within project",
"end": 33,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 33,
"label": "Task answer",
"end": 39,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 39,
"label": "Cross-device proposition",
"end": 44,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 44,
"label": "Team message",
"end": 50,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 50,
"label": "Project overview",
"end": 56,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 56,
"label": "Review results",
"end": 61,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 61,
"label": "Brand",
"end": 64.033333,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
}
],
"duration": 64.033333,
"fontFamily": "Georgia, serif"
}
```