> 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/charts-trellis-layout.md).

# Charts trellis layout

In small multiples mode, you can choose from different layouts to display charts.

* **Grid**: The data is displayed in a row-by-column grid with panels of equal size with uniform scaling.
* **Grid auto-fit:** The maximum possible data is rendered in the space available on the canvas, without scroll and pagination depending on the data volume.
* **Scaled rows:** The height of a row will be scaled according to the top-performing panel, rows can be of different heights based on the magnitude of the data in each panel. This layout is only applicable to vertical chart orientations.
* **Ranked panels:** The panel size varies based on the magnitude of the measure. This layout can be applied when you have a single small multiple parameter and it is assigned to the column bucket.

{% hint style="info" %}
Interactive resizing is available in the grid and grid auto-fit layouts. You can drag the sides to resize the panels.
{% endhint %}

<figure><img src="https://3132984990-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOoZhPvC57Z0CNgep4Ib%2Fuploads%2Fe6blNW6HT421jCt0TNb1%2FUntitled%20design%20(8).gif?alt=media&amp;token=f66c2469-7381-4ce4-86d9-a6e44c3d2f73" alt=""><figcaption><p>Charts trellis layouts</p></figcaption></figure>


---

# 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/charts-trellis-layout.md?ask=<question>&goal=<user_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.