> 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/cards-trellis-layout.md). # Cards trellis layout The various trellis layouts for cards are intended to guide the viewer through the metrics that you wish to highlight: * **Grid**: The data is displayed in a row-by-column grid with panels of equal size with uniform scaling. * **Compact grid:** This layout renders cards in compact stamp-sized panels. Due to efficient real-estate usage on the canvas, this layout is ideal for combining KPI cards with other visuals in a dashboard. * **Single row:** All the cards will be accommodated in a single row. * **Single column:** The chart and metrics are displayed side-by-side in this layout. The wide spacing enhances readability and facilitates comparative analysis between metrics. You can position the KPI metrics to the left or right side of the chart. {% hint style="info" %} Interactive resizing is available in the grid and compact grid layouts. You can drag the sides to resize the panels. In the single-column layout, interactive resizing is available to adjust the card's height. In the single-row layout, interactive resizing is available to adjust the card's width. {% endhint %}

Trellis layouts for cards

--- # 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/cards-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.