Supabase Explorer and Notebooks
Open the product through a growth chart, then demonstrate queries, saving, natural language and local workflows in turn, keeping short phrases beside the feature being shown.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Supabase Explorer and Notebooks · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090b0b}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
One capability statement on the left, one operation on the right
After the product name is revealed, keep the short statement area fixed on the left, with the corresponding operation shown in a dark interface on the right. The interface may tilt slightly and move slowly forward, but the main SQL and results areas must stay within reading range.
The data table and chart share the same query
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Supabase Explorer and Notebooks · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090b0b}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="28.5" data-end="36"><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 the query first, populate the table after it runs, then switch to a green chart. Keep the note title in the save segment to show that the query, data, and chart belong to the same unit of work.
Natural language ultimately resolves into visible SQL
After a question is entered, show the generated query and results; end the local-repository segment with a separate terminal command. A black background, gray-white body text, monospaced code, and restrained green establish a stable hierarchy. Do not let neon glow reduce text contrast.
Use a complete data story when adapting
When replacing the project name, query, table, and chart, keep fields and values consistent. Explain one actionable capability per segment, maintain the fixed short statement area, and end by showing how the result is saved or taken away.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- When replacing the project name, query, table, and chart, keep fields and values consistent. Explain one actionable capability per segment, maintain the fixed short statement area, and end by showing how the result is saved or taken away.
Production constraints
Tilted interface / User-growth chart / SQL editor / Results table / Natural-language input / Local command
- Open the product through a growth chart, then demonstrate queries, saving, natural language and local workflows in turn, keeping short phrases beside the feature being shown.
- After the product name is revealed, keep the short statement area fixed on the left, with the corresponding operation shown in a dark interface on the right. The interface may tilt slightly and move slowly forward, but the main SQL and results areas must stay within reading range.
- Show the query first, populate the table after it runs, then switch to a green chart. Keep the note title in the save segment to show that the query, data, and chart belong to the same unit of work.