> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/components/common-controls/link.md).

# Link

Link a component to a page, resource, anchor, email address, or website

The Link control makes a supported component clickable. Elements tracks internal pages, anchors, and resources so their published destinations stay current when the project changes.

{% embed url="<https://youtu.be/mt-5Zhk3M7E>" %}

### Link Panel

Choose **To** or **Choose Link…** to open the Link panel. An unset link is the default. Use the Clear button to remove an existing destination.

{% columns %}
{% column width="50%" %}
Available link types include:

* **URL** — Links to an external URL. Entering an email address creates a `mailto:` link.
* **Plain** — Uses the entered destination without Elements resolving it; useful for specialised or generated URLs.
* **Page** — Links to a page in the project.
* **Anchor** — Links to a component ID on a selected page.
* **Resource** — Links to a file stored in Resources.
  {% endcolumn %}

{% column width="50%" %}

<figure><img src="https://3876014504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy6AECEVH2p4eFDicpM1%2Fuploads%2FNIK13Wmct5QUen6mmABm%2FCleanShot%202025-11-01%20at%204%E2%80%AF.16.10%402x.png?alt=media&amp;token=08b532e2-dd26-49e3-872c-321c33114ce9" alt="The Elements Link panel with destination options"><figcaption><p>The Link panel selects and manages destinations.</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Email Links

Entering an email address creates a `mailto:` destination. Test it in a browser because the visitor must have an email application configured.

### Custom Attributes

Where the Link panel provides Custom Attributes, add a Name and Value for attributes such as:

| Name    | Example value           | Purpose                                                  |
| ------- | ----------------------- | -------------------------------------------------------- |
| `title` | `Go to Example Website` | Supplies additional advisory text.                       |
| `rel`   | `noreferrer`            | Prevents the destination receiving referrer information. |
| `rel`   | `nofollow`              | Asks search engines not to follow the link.              |
| `type`  | `application/pdf`       | Identifies the linked resource’s MIME type.              |

Use one `rel` attribute with space-separated values when more than one relationship is required, for example `nofollow noreferrer`.

### Linking to an Anchor

1. Select the destination component.
2. Enter a unique value under **Advanced → ID**.
3. Open the Link panel on the source component or selected inline text.
4. Choose the destination page.
5. Choose the component ID from the Anchor list.

On the same page, the published destination uses a fragment such as `#about-section`.

{% embed url="<https://youtu.be/VEqrlcXydTs>" %}

{% hint style="warning" %}
Elements sites use smooth anchor scrolling by default. To disable it site-wide, remove `class="scroll-smooth"` from the `html` tag in the site Template code.
{% endhint %}

### Accessibility

Use link text that describes the destination. Avoid making a Container clickable when it contains Buttons, links, form fields, or other interactive controls.


---

# 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.realmacsoftware.com/elements-docs/using-elements/components/common-controls/link.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.