> 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/elements-language/component/shared-files/assets.md).

# Assets

The `assets` folder stores files that are shared across multiple components in your element pack. Assets are **not automatically included** in the page—they must be referenced from a [shared template](/elements-docs/elements-language/component/shared-files/templates.md).

## Supported Asset Types

| Type       | Examples                                              |
| ---------- | ----------------------------------------------------- |
| JavaScript | Libraries (Alpine.js, GSAP), utility scripts, plugins |
| CSS        | Stylesheets, resets, utility classes                  |
| Images     | Icons, placeholders, UI graphics                      |
| Fonts      | Custom web fonts                                      |
| Other      | Any static file your components need                  |

## Folder Organization

You can organize assets into subdirectories for better structure:

```
shared/
  assets/
    alpine.js
    gsap.min.js
    styles.css
    images/
      icon.webp
      placeholder.jpg
    fonts/
      custom-font.woff2
```

## Linking to Assets

Use the `{{assetPath}}` variable in your shared templates to reference assets. This resolves to the correct path at build time.

**JavaScript:**

```html
<script src="{{assetPath}}/library.js"></script>
```

**CSS:**

```html
<link rel="stylesheet" href="{{assetPath}}/styles.css">
```

**Images:**

```html
<img src="{{assetPath}}/images/icon.png">
```

{% hint style="info" %}
Assets are only accessible when referenced from a shared template. Place the template in the appropriate injection folder (`headStart`, `headEnd`, `bodyStart`, or `bodyEnd`) based on when the asset should load.
{% 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.realmacsoftware.com/elements-docs/elements-language/component/shared-files/assets.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.