> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/help-and-faqs/can-i-attach-a-link-to-an-entire-banner.md).

# Can I attach a link to an entire banner?

### What you are trying to do <a href="#what-you-are-trying-to-do" id="what-you-are-trying-to-do"></a>

You want a whole slideshow slide to be clickable, so a customer who taps anywhere on the image lands on the collection or product it advertises, rather than having to aim at a small button.

### The short answer <a href="#the-short-answer" id="the-short-answer"></a>

Not with the built in settings. The theme does not support adding a link to an entire **Slideshow** slide. Only individual elements inside the slide, such as a button, can be linked through the Theme Editor.

### What you can do instead <a href="#what-you-can-do-instead" id="what-you-can-do-instead"></a>

**Link the button and make it easy to hit.** A clear button label is what most customers look for anyway, and it tells them where they are going before they tap. Give the button wording that names the destination, for example *Shop skincare* rather than *Learn more*.

**Ask for a customization.** If the whole slide really has to be clickable, our technical support team can help you with it.

### When to contact support <a href="#when-to-contact-support" id="when-to-contact-support"></a>

Contact support when you want the full slide made clickable, or when a link you did set on a button inside a slide does not work, opens the wrong page, or cannot be tapped on mobile.

Send this with your first message:

* Your store URL, and the URL of the page holding the banner.
* Which slide it is, counting from the first one, and where each slide should link to.
* A screenshot of the slide with the clickable area you want marked on it.
* Theme name and version: **Vélare 1.0.0**, shown under the theme name in **Online Store > Themes**.
* A [staff account](/velare/help-and-faqs/staff-account.md) for the support team, since this needs a change inside the theme.

{% hint style="info" %}
A customization like this is code added on top of the theme. Keep a note of it, because custom code is not carried over by the one click update and has to be reapplied afterwards.
{% endhint %}

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Slideshow](/velare/customize-your-pages/banners/slideshow.md): every setting for the Slideshow banner, including the button link
* [Button](/velare/customize-your-pages/basic/button.md): the block that carries the link inside a slide
* [Image with text overlay](/velare/customize-your-pages/banners/image-with-text-overlay.md): another banner section, if a single image suits you better than a slider
* [Staff account](/velare/help-and-faqs/staff-account.md): how to give the support team access to your store


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uxsmart.gitbook.io/velare/help-and-faqs/can-i-attach-a-link-to-an-entire-banner.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.