> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/analytics+/working-with-analytics+/6.-trellis-customizations/tables-trellis-layout.md).
# Tables trellis layout
Analytics+ provides different layouts for small multiple tables:
* **Grid**: The data is displayed in a row-by-column grid with panels of equal size with uniform scaling.
* **Scaled table:** The size of each panel is determined by the number of rows and columns in the table.
* **Single row:** All the small multiple tables will be accommodated side-by-side in a single row.
* **Single column:** All the small multiple tables will be rendered one below the other in a single column.
{% hint style="info" %}
Interactive resizing is available in the grid layout. You can drag the sides to resize the panels.
{% endhint %}
Trellis layout for tables
---
# 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.inforiver.com/analytics+/working-with-analytics+/6.-trellis-customizations/tables-trellis-layout.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.
