# Reading Tracks (/docs/tracks)



These docs are organised by **subject** — connectors, strategies, agents,
billing. Most readers arrive with an **audience** instead: they want to
understand the model, or drive the product, or extend the engine, or keep it
running. Almost every subject section serves two or three of those at once.

So rather than split the tree, every page declares the one audience that
cannot do its job without it. Pick the track that matches why you're here.

<Cards>
  <Card title="Understand it" href="/docs/tracks/explainer">
    The model — what a thing is and why it works that way. Start here if the vocabulary is new.
  </Card>

  <Card title="Click it" href="/docs/tracks/nocode">
    Build routes in the visual editor, without writing code or calling an endpoint.
  </Card>

  <Card title="Call it" href="/docs/tracks/api">
    Drive Ductor over REST, Connect-RPC, or the CLI. The largest track.
  </Card>

  <Card title="Extend it" href="/docs/tracks/code">
    Write Go, TypeScript, or Python against the engine — SDKs, strategies, providers.
  </Card>

  <Card title="Run it" href="/docs/tracks/operate">
    Deploy, migrate, monitor, secure, and recover a running instance.
  </Card>
</Cards>

## Tracks are a lens, not a location [#tracks-are-a-lens-not-a-location]

A page's track is metadata, not its address. `connectors/connections` stays
where it is; it simply announces that it is written for someone calling the
API. Nothing moved, and no link you have already saved has changed.

That also means the tracks overlap by design. A page can name a secondary
audience, and many do — an explanatory page that ends with a worked `curl`
call belongs to **Understand it**, and points at **Call it** as well.