> 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/customize-your-pages/links.md).

# Links

The **Links** group holds the block for content that opens over the page instead of loading a new one. Like every block here, it is added inside a section, so the trigger sits exactly where the question comes up and the answer arrives without the shopper losing their place.

This is the group to use for the supporting content shoppers ask for at a specific moment: a size guide next to the size selector, delivery terms next to the price, care instructions next to the fabric.

### How to add a link block <a href="#how-to-add" id="how-to-add"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Online Store > Themes > Customize**.
2. In the left sidebar, click the section where the trigger should sit.
3. Click **Add block** and choose **Popup link**.
4. Write the link text, choose whether it opens as a popup or a drawer, then add the blocks that fill it.
   {% endhint %}

*Result:* the link appears in the section, and clicking it in the preview opens the container with your nested blocks inside.

### Blocks in this group <a href="#blocks-in-this-group" id="blocks-in-this-group"></a>

| Block                                                          | What it does                                                                                             | Reach for it when                                                                                                                          |
| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| [Popup link](/velare/customize-your-pages/links/popup-link.md) | Shows a piece of text, a button, or an icon that opens a popup or a side drawer built from nested blocks | Extra detail is worth having on hand but not worth taking up room on the page, and sending shoppers to another page would break their flow |

### Choosing how it opens <a href="#choosing-how-it-opens" id="choosing-how-it-opens"></a>

1. A popup suits short content read at a glance, such as a table or a paragraph.
2. A drawer suits longer content shoppers scroll through, since it slides in from the side and leaves the page recognisable behind it.
3. If the content deserves its own address that shoppers can search for or link to, use a [Button](/velare/customize-your-pages/basic/button.md) pointing at a real page instead.

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

* [Button](/velare/customize-your-pages/basic/button.md): for actions that load a page rather than open an overlay
* [Basic](/velare/customize-your-pages/basic.md): the content blocks that fill a popup
* [Layout](/velare/customize-your-pages/layout.md): the containers for arranging that content once it is inside


---

# 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/customize-your-pages/links.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.