> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/coda-webstore-builder/readme.md).

# Readme

The AI Store Builder generates a complete, working webstore for your game, which you then shape and control yourself.

Generation gets you to a functioning storefront—catalogue, categories, payment flow, descriptions, FAQs—in minutes. Everything the AI produces is a starting point, not a fixed output. You can rearrange it, restyle it, override individual elements down to the pixel, and test it end to end before anything reaches your players.

## What you can control

| Area                   | What you can do                                                                                           | Where it's documented                                                                                                          |
| ---------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Layout                 | Reorder the major sections of your store, your categories, and the SKUs within each category              | [Arranging your store layout](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-layout-configuration.md)          |
| Appearance             | Select any element on the page and override its colour, imagery, typography, shape and interaction states | [Customising elements](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-design-customization.md)                 |
| Catalogue presentation | Choose SKU box styles, set SKU width, add motion and particle effects                                     | [Presenting your catalogue](https://docs.coda.co/coda-webstore/coda-webstore-builder/catalog-design-configuration.md)          |
| Navigation and trust   | Category banners, category menu, the Official Store marker, country and language switching                | [Navigation and trust markers](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-navigation-and-trust-markers.md) |
| Testing                | Run real test transactions in sandbox, and point validation and top-up at the environment you choose      | [Testing your store](broken://pages/7b170de7dec87e56ecddbb55d6da1cd9abecc4d4)                                                  |

## How changes reach your players

Every change you make is saved to your **sandbox** store first. Nothing you do in the builder affects your live store until you explicitly publish it.

This means you can rearrange your layout, try three different SKU treatments, run test transactions against the result, and only then push it to production. See [Sandbox and publishing](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-sandbox-and-production-environment.md).

## Where you work

All of the controls described in this documentation live in **Coda Portal**.


---

# 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://docs.coda.co/coda-webstore/coda-webstore-builder/readme.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.
