> 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/store-design-customization.md).

# Store Design Customization

The AI Store Builder generates a complete visual treatment for your store. If any part of that treatment isn't right for your brand, you can select it and override it yourself.

This applies to every element on the page. There is no fixed list of “customisable” components—if you can see it, you can select it and change it.

## What you can select

Among others:

* Buttons
* Text blocks and headings
* The navigation bar
* SKU boxes
* Category banners
* Input fields
* Section backgrounds

Select the element you want to change, and the available overrides for that element become editable.

## What you can change

**Colour and imagery.** Replace a generated background with a solid colour, upload your own image, or use an animated GIF. This applies to the navigation bar, section backgrounds, SKU boxes and banners.

**Typography.** Change the font family and the font colour. Your brand typeface should be your brand typeface, not an approximation of it.

**Shape.** Adjust the shape of boxes and containers on the page—corners, borders and edges.

**Motion.** Add animated effects such as running borders and shimmer. Motion is one of the more effective ways to make a storefront feel like part of your game rather than a payment page attached to it. See [Presenting your catalogue](https://docs.coda.co/coda-webstore/coda-webstore-builder/catalog-design-configuration.md) for SKU-specific effects.

## Interaction states

Styling isn't limited to how an element looks sitting still. For interactive elements—buttons and input fields—you can style each state independently:

* **Default** — how the element looks at rest
* **Hover** — how it looks when a player moves a cursor over it
* **Pressed** — how it looks at the moment of a click or tap

This is usually the level of detail a brand team works at, and it's the difference between a store that approximately matches your identity and one that actually does.

## Working safely

Every override is saved to your sandbox store first. Restyle as much as you want, view the result as a player would see it, and publish only when you're satisfied. See [Sandbox and publishing](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-sandbox-and-production-environment.md).


---

# 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/store-design-customization.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.
