# Concepts
Source: https://docs.aden.space/docs/developers/concepts

How tracks, albums and teams are modeled, and how to drive them from the API.
These pages explain Aden's core resources in detail: the data
model, the lifecycle, and the endpoints that drive them. Use them when you're
building an integration that goes beyond a single endpoint and want to
understand how the pieces fit together.

<Cards>
  <Card title="Tracks" href="/docs/developers/concepts/tracks" description="Versions, covers, collaborators, comments, todos, and the release lifecycle." />

  <Card title="Albums" href="/docs/developers/concepts/albums" description="Group tracks into releases, manage collaborators, and ship a record." />

  <Card title="Team" href="/docs/developers/concepts/team" description="Members, invites, plans, socials, and the shared workspace model." />
</Cards>

## How to read these pages [#how-to-read-these-pages]

Every feature page follows the same shape:

* **What it is**: the concept and where it shows up in the product.
* **Data model**: the resource, its key fields, and how it relates to others.
* **Lifecycle**: the states a resource moves through and what triggers them.
* **Endpoints**: the relevant API surface, grouped by intent.
* **Recipes**: short, copy-paste SDK snippets for the common jobs.

For the full request/response schema of any endpoint, jump to the
[API Reference](/docs/developers/api).