> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/introduction/how-to-use-this-documentation.md).
# How to use this documentation
## How to use this documentation
The documentation is divided into short pages that describe specific tasks. This makes it possible to quickly find instructions for one activity without reading the entire manual.
### Task page layout
A typical instruction page has the following layout:
| Section | Meaning |
| --------------------- | ----------------------------------------------------------------------- |
| Purpose | A short explanation of what the function is used for. |
| Menu path | The place in the system where the user should start. |
| When to use | Situations in which the function is needed. |
| Steps | Step-by-step instructions. |
| Required fields | Data that must be filled in. |
| Notes and limitations | Information about dependencies, statuses, permissions or common errors. |
### How to read menu paths
Menu paths are written in this format:
```
Administration -> System -> Users
```
This means that the user should open `Administration`, then select `System`, and then open the `Users` screen.
### How to read screenshots
The documentation uses screenshots that show selected backend screens. Screenshots were prepared using the same interface layout:
| Setting | Value |
| ------------------------ | ------------------------------ |
| Theme | Modern |
| The location of the menu | On the left side of the screen |
The screen layout can be changed in the system under:
```
Application -> Preferences
```
If a user works with a different theme or with the menu at the top of the screen, function names remain the same, but the position of elements may differ from the screenshots in this documentation.
The screenshot below shows the names of the most important screen areas used in the instructions.
### Main screen elements
| Element | Description |
| ------------------ | -------------------------------------------------------------------------- |
| System menu | The left-side menu with the main system areas. |
| Login details | Information about the logged-in user, current location and open screen. |
| Main area | The main part of the screen where the user performs operations. |
| Filter / form | A form or filter section used to narrow the data list or fill in criteria. |
| Data/results table | A list of records matching the search criteria. |
| Tabs | Additional detail sections, such as document items, prices or attributes. |
| Action buttons | Buttons used to add, edit, delete, save, confirm or print. |
{% hint style="success" %}
If you do not know where to start, use GitBook search and enter the task name, for example `add user`, `change price`, `promotion` or `document list`.
{% 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.aquiladynamics.com/aquila-store-user-manual/introduction/how-to-use-this-documentation.md?ask=&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.
