Files

# Guides

**What goes here:** Task-oriented, step-by-step content. "How do I do X with
ClickHouse?" Each page should have a clear goal and a sequence of steps a
reader can follow.

**Audience:** Users who already have ClickHouse running and want to accomplish
something specific — building a pipeline, optimizing a query, hardening a
deployment.

**Subdirectories:**
- `clickhouse/` — guides applicable to both Cloud and self-managed ClickHouse
  (data modelling, performance, working with arrays/joins, examples).
- `use-cases/` — guides grouped by use case (AI/ML, data warehousing,
  observability, real-time analytics).
- `oss/` — guides specific to self-managed ClickHouse (deployment, scaling,
  upgrades, best practices).

If a page explains *how something works* rather than *how to do something*,
it belongs in `/concepts`. If it's reference material (settings, function
signatures), it belongs in `/reference`.