> 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/video-banners.md).

# Video Banners

Coda can generate video hero banners for your store using AI, producing a moving banner in place of a static image.

The video is generated from your game's metadata. A language model first works out the structure the video should take for your specific title—its length and its opening, middle, and closing sections—and that structure, along with sample assets, is used to produce the finished banner.

A hero banner that moves changes how a storefront reads. It's the difference between a page that looks like a payment form and one that looks like it belongs to your game.

## Availability

{% hint style="info" %}
This feature is **not enabled by default**. If you'd like a video hero banner for your store, speak to your Coda contact.
{% endhint %}


---

# 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/video-banners.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.
