> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/assetics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/assetics/assets-the-functions.md).

# Assets: the Functions

XOOPS has historically provided two methods in the XoopsTheme class to deal with assets:

```
addScript($url)

addStylesheet($url)
```

Note that these methods expect URLs, not filesystem paths.

**New Assets Functions**

The XoopsTheme class has been expanded to better manage assets. The following methods are available:

```
addScriptAssets($assets, $filters)
addStylesheetAssets($assets, $filters)
addBaseScriptAssets($assets)
addBaseStylesheetAssets($assets)
setNamedAsset($name, $assets, $filters)
```

Let's review now these functinos individually:

**addScriptAssets & addStylesheetAssets**

Accept an array of one or more asset file specifications Optionally accept a string of comma separated filter names Result in combining and filtering the assets, then adding the URL for the created static asset file to the same lists used by **addScript()** and **addStylesheet()**

**addBaseScriptAssets & addBaseStylesheetAssets**

Accept an array of one or more asset file specifications

Accumulate asset files in separate lists, similar to addScript() and addStylesheet()

Assets are processed using default filters and the resulting static file URL is added to the top of respective list in the page headers:

```
<{$xoops_module_header}>
```


---

# 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://xoops.gitbook.io/assetics/assets-the-functions.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.