> 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/header/header/navigation-images.md).

# Navigation images

Enhance your navigation menu with images, products and collections

With Pipeline, incorporating images into your Navigation is a breeze. You have the option to create a drop-down menu with images only or a mix of menu items and images.

Customers will be able to find your featured products faster and easier with these promotions:

<div data-full-width="false"><img src="https://3528441459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LovEU3LvzkJzFkXarYD-4120580575%2Fuploads%2FDbqP2caABSEzkMVH8wgE%2Fpipeline-nav.png?alt=media&amp;token=ee70f67c-d817-496f-b5ea-d6a7a3d8db94" alt="Collection products in navigation"></div>

Images, products, and collections are added as blocks to the Header. Choose which menu item numerically and add content.&#x20;

### Blocks

Add from a range of block styles with various options to customize your navigation:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Image</strong></td><td>Add any image from your library with an optional heading, button and link</td></tr><tr><td><strong>Product</strong></td><td>Select a particular product to display with instant Add to Cart functionality</td></tr><tr><td><strong>Collection</strong></td><td>Add a group of products instantly to the header navigation</td></tr></tbody></table>

### Video

A complete overview of how to add, position, and customize header blocks in Pipeline:

{% embed url="<https://www.loom.com/share/273bc913041a4e25964f1ec9818f0f4d?sid=22545dcd-cc57-4813-bdcc-ff6b38e993db>" fullWidth="true" %}


---

# 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/header/header/navigation-images.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.