> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/products/display-only-media-related-to-the-chosen-variant.md).

# Display Only Media Related to the Chosen Variant

Filter the Volume product gallery by selected variant: add the color name in parentheses to each image's alt text to link it to that variant.

Focus visitors’ attention on images of the selected product color within the gallery on Product pages.

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2FNuyS43klip6Lo7A8w0Kz%2Fonly-media.gif?alt=media&amp;token=f5b6088c-6840-467d-99db-a905876c75de" alt=""><figcaption></figcaption></figure>

The solution lies in linking the variant image with other images of the same color in the Media library. We'll connect them through the Alt text of the images.

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2FRil458MvZ8fA0UPepLD9%2Fclean%20up!.gif?alt=media&amp;token=40a4d5d6-3343-47d0-863f-38c9e2ffbdb2" alt=""><figcaption></figcaption></figure>

1. In Media, find the image associated with the variant.
2. Click Edit, and in the window that opens, click Add alt text.
3. The alt text can be anything. In parentheses, write the color name, like `(Black)`, and save it.
4. Now, find another image of this black color and duplicate the prefix `(Black)` after its alt text.
5. Remember to save the changes on the product page.

Repeat this process with all images in Media.


---

# 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://staylime.com/docs/volume-themes/products/display-only-media-related-to-the-chosen-variant.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.
