Perplexity AI / Snowflake Integration — Computer now…
Derive questions from existing business data, then show connections, queries, and reports. Data cards attract attention; queries explain where results come from.
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 AI / Snowflake Integration — Computer now… · 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
Establish the business question before connecting data
Open with a few key metrics and one problem statement, then connect the data source. Alternate headings and actions to clearly segment the complex database process.
Finish connecting before retrieval begins
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 AI / Snowflake Integration — Computer now… · 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="13" data-end="25"><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 source marker, connection action, and success state in one local area. Ask the team question after connecting, retaining the source name as context for later reports.
Keep queries and reports aligned
Show only code essential to the result, immediately followed by its table or metric. Keep field names, units, and report headings consistent so viewers can follow questions to conclusions.
| Visual content | Production focus |
|---|---|
| Question | One clear business subject and time range |
| Query | Matching fields, filters, or aggregation |
| Report | Metrics and conclusions answering the question |
| Output columns | Summarize deliverables from the same business chain |
Keep whitespace despite abundant data
Organize with pale warm color, fine lines, and teal accents; use serif main headings, monospaced code, and sans serif tables. Focus each close-up on one query or report area; do not shrink long tables into unreadable thumbnails.
Change fields together with the business
Adapt to sales, support, or R&D data. Replace sources, questions, query fields, and final figures together; keep displayed data internally consistent rather than merely renaming reports.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to business-data assistants while preserving source traceability.
Production constraints
Metric card / database connection / question / SQL snippet / report / output columns
- Introduce a question from existing data cards, then show query and report evidence after connecting the data source.
- Show code and reports only in their corresponding stages, using proposition pages as pauses.