> For the complete documentation index, see [llms.txt](https://pipeline.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pipeline.groupthought.com/sections/list-of-sections/gallery.md).
# Gallery
Elegant image gallery section for Lookbooks and more
Quickly build an image gallery utilizing Pipeline's design language. The Gallery section is an easy-to-build section that includes many features to manage the layout, and user interaction:
Complement with the Gallery text section to add captions:
Easily add captions with Gallery text section
### Section settings
Use the section settings to adjust image scaling, background color, padding (gutters), multi-image progress bar, items per row for different device types, and section padding:
Images are sized down if the Items per row setting is set high. Larger images with scrolling are displayed when the Items per row setting is set lower:
### Block settings
Add image blocks to the section and customize with image choice, positioning, and optional link:
A pop-up video player is displayed when a YouTube or Vimeo link is used.
If the link is empty, the image will zoom. You can also link to a local or external page when a URL is used.
---
# 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://pipeline.groupthought.com/sections/list-of-sections/gallery.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.
