> ## Documentation Index
> Fetch the complete documentation index at: https://dev.almedia.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started

> The path from deciding to integrate to a player completing their first link — about 15 minutes of engineering time.

Getting to a first link takes about **15 minutes** of engineering time. Most of the calendar
time goes to the commercial and attribution setup around it, which can happen in parallel.

## Pick your path

<CardGroup cols={2}>
  <Card title="I am building the integration" icon="terminal" href="/technical/integration-guide">
    Go to the integration guide. It is synced from the SDK repository, so it matches the code
    you are about to install.
  </Card>

  <Card title="I am getting us ready to launch" icon="clipboard-check" href="/publisher/prerequisites">
    Start with prerequisites — accounts, attribution and the decisions to make before
    engineering begins.
  </Card>
</CardGroup>

## What happens, in order

<div className="al-todo">
  **TODO(copy)** — the end-to-end sequence, from first conversation to live.

  This is deliberately prose with subheadings rather than a numbered `<Steps>` component. Steps
  renders as a CLI install wizard, which reads wrong for a mixed commercial and technical
  audience — it is reserved for the [Technical Docs](/technical).

  Needed: the real ordering, who owns each stage, and roughly how long each takes. The only
  timing figure currently approved is the \~15 minutes of engineering work for the SDK
  integration itself.
</div>

## Before you start

Worth having in place first — the full list is on
[prerequisites](/publisher/prerequisites):

<div className="al-todo">
  **TODO(copy)** — the short version of the prerequisites list, three or four items. Keep it a
  summary; the page it links to owns the detail.
</div>

<Callout icon="life-buoy">
  **TODO(copy)** — support route. Who does a publisher contact when they get stuck, and
  through what channel? No support address appears in the source material, so none is invented
  here.
</Callout>