> 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/image-banner/collage.md).

# Collage

Introduced in Pipeline 7.2

The collage block in Pipeline helps you add an extra layer of images over your image banner section. With the shape options, you can create custom designs that resemble stickers or unique image layouts:

<figure><img src="https://3528441459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LovEU3LvzkJzFkXarYD-4120580575%2Fuploads%2F7HCd7C16Jic4JMZ527Ku%2Fcollage%20block.jpg?alt=media&amp;token=438b67d5-6455-4125-93d3-25c177da0f07" alt=""><figcaption></figcaption></figure>

Add a new collage block for each image. Customize each block independently with settings for:

* Image width
* Shape
* Horizontal and vertical positioning
* Option to display or hide on mobile

The image position sliders allow you to place the block in any position you like over the main banner image. Experiment with sizes, shapes and positions for a completely flexible promotion.&#x20;

### Pipeline image shapes

Video overview of the custom shape options:

{% embed url="<https://www.loom.com/share/bf892561adfa47169125954901b2f269?sid=a8b14647-3bb1-4b4f-9ab8-d31b22e8ccc2>" %}


---

# 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/image-banner/collage.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.
