Open SQL Playground first when you want browser-only reps, a teaching surface, or a fast way to reduce query-shape anxiety before you touch the warehouse.

Start on Analytics Quickstart when you already have the file or want the shortest route to one live query, one dataframe, or one standings read you can reuse.

Open

first when the job is build setup, docs work, or choosing the right entry page before a code change.

Use Daily Updates for recurring work, then move to Troubleshooting Playbook only when you need the exact artifact, report, or failed command that explains the miss.

Best for choosing the right first page and command by role. Typical next stop: Installation, CLI Reference, or Schema Reference.

Best for getting from download to first answer. Typical next stop: DuckDB Query Examples or Player Comparison.

Best for DuckDB-WASM practice with self-contained NBA-flavored sample data. Typical next stop: Analytics Quickstart or DuckDB Query Examples.

Use this when you want copy-ready query patterns. Typical next stop: Schema Reference or Table Lineage.

Use this when the question is player-versus-player framing. Typical next stop: Shot Chart Analysis.

Use this when location and shot-zone patterns matter. Typical next stop: Column Lineage.

Use this when the workflow lives in Polars, Pandas, or Arrow. Typical next stop: Schema Reference.

Keep this open for recurring pipeline runs and operational checks. Typical next stop: Troubleshooting Playbook .

Use this when the task shifts from local shape to packaging and publish flow. Typical next stop: Architecture.

Use this when you need a narrow recovery loop for a broken artifact, failing command, or quality miss. Typical next stop: the exact health artifact, coverage report, or docs-autogen command that explains the issue.