> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/project-data/stages.md).

# Stages

Stages are similar to Catalog Items in that they reference an asset from the Asset Library. Specifically, stages reference Scene Assets. Stages are meant to be the means by which the merchandiser collaborates with the artist to address product placement, lighting, position, rotation, camera angles, etc; essentially, all elements involved in staging the product.<br>

<figure><img src="https://2668731230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fknvt0jlDBXmk91mWaWXB%2Fuploads%2FISxdEUs4VZRf9g0QBH3Y%2FStages_1.png?alt=media&amp;token=28fa7f07-93c5-4785-8716-c0e9e85d29a8" alt=""><figcaption></figcaption></figure>

Stages will typically require a placeholder to dictate where a product should be placed. Beyond that bare minimal setup, the artist is free to expose scene properties for manipulation in accordance with the attributes created on the Stage, via the same process as creating a configurator.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community.threekit.com/platform-documentation/project-data/stages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
