> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2022/spring-22-release/grid-views.md).
# Grid Views
Browse your Product Catalog, Visual Assets, and Stages visually with two new Grid views.
Switch to one of the two Grid View sizes using the icons to the top right of the Table View header.
Grid View displays records in a card view with relevant metadata like Tags, Published State, or Asset Type.
Grid Views can be sorted using the sort dropdown.
Cards can be selected individually or in bulk using the checkboxes. Then, you can perform bulk actions.
For Assets, hovering over a Card exposes a link to launch the Editor directly.
Your selection is saved per page so that you can have one view for Items, one for Assets, and one for Stages.
---
# 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://community.threekit.com/releases/2022/spring-22-release/grid-views.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.
