> For the complete documentation index, see [llms.txt](https://docs.admira.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.admira.com/english/contents/html-content/file-structure.md).

# File structure

The current file structure for playback over HTML5 player limits the use of subfolders. Any files needed for the HTML content must remain in the same folder as this, including css, js, png, jpg, mp4, ogg, etc.

That is, the structure would be:

* *main\_12345.html*
* *script\_12345.js*
* *image\_12345.png*
* *style\_12345.css*
* *….*

By not being able to use subfolders, the correct naming of files is essential, with each content being a unique file with its associates that are also unique. The example uses “12345” to uniquely identify the content.

{% hint style="warning" %}
**Important**

File names of attached scripts **cannot contain the period sign (“.”)**. That is, names like "socket.io.js" are not accepted, but it must be uploaded renamed as "socket\_io.js"
{% 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 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://docs.admira.com/english/contents/html-content/file-structure.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.