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

# Element Labs documentation

> Install, configure and operate Element Labs products on your FiveM server.

Element Labs products are FiveM resources. Each one is a directory you drop into your server, and
all of them share one installed resource, `element_sdk`, that they need to run.

## Where to start

<Steps>
  <Step title="Check the requirements" icon="list-check">
    Confirm your server meets the [requirements](/getting-started/requirements). A product that
    needs a framework does not start without one.
  </Step>

  <Step title="Install the SDK and the product" icon="download">
    Follow [Install a product](/getting-started/installation) for the SDK and your first product.
  </Step>

  <Step title="Configure it" icon="sliders">
    Change the product's behaviour through the files in its `configs` directory. The rules are in
    [Configuration files](/sdk/configuration); the individual settings are on the product's own
    pages.
  </Step>
</Steps>

## How this documentation is organised

<CardGroup cols={2}>
  <Card title="Get started" icon="rocket" href="/getting-started/requirements">
    Requirements, installation, updating and licensing.
  </Card>

  <Card title="Concepts" icon="diagram-project" href="/concepts/architecture">
    How an installation fits together, what a resource contains, how versions work.
  </Card>

  <Card title="SDK" icon="cube" href="/sdk/index">
    The behaviour every product shares: configuration, languages, versions, supported resources,
    server settings.
  </Card>

  <Card title="Support" icon="life-ring" href="/support/index">
    Diagnosing problems, the meaning of console messages, contacting us.
  </Card>

  <Card title="One tab per product" icon="box-open">
    Everything specific to that product: installation, settings, reference and its own
    troubleshooting.
  </Card>
</CardGroup>

Anything that behaves the same across every product is documented once, in the SDK section. Product
pages link to it rather than repeating it, so there is one place to check when a behaviour surprises
you.

## When something goes wrong

Start at [Diagnosing a problem](/support/index). It works from what you see (a failed start, a
setting with no effect, wrong text on screen) to the page that fixes it.