# Directory: static

The **optional**`static` directory can be used to store any non-XML local content, for example images and prefabricated PDF. You may use subdirectories.

## Images in PDF

On inserting images into PDF, the `static` directory serves as the local root path to the XSLT processor. So you can either use an absolute path (URL) or a relative (local) path that refers to this directory.

## Images in Email Body

If the email-body has a content type like `text/html; charset=utf-8` then it may include tags such as `<img src="cid:foo/bar.jpg">`. The tag is most commonly an \<img>, but can be any tag. The system then searches in the static directory for any file with that path. The file is included with the image, as a “related” multi-part part, meaning the file is available to the HTML document as an "inline image" when its rendered in the email client. Don't forget the `cid:` text in the `src` attribute!

## Return Static Files

Instead of returning content from XSLT transformation, you may also return “prefabricated” content from this directory. The syntax `<response-from-static filename="path-to-file"/>` returns a file from this directory.


---

# Agent Instructions: 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:

```
GET https://onestopconcept.gitbook.io/open-endpoints/configuration/application-directory-structure/directory-static.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.