> 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/logo-list.md). # Logo list Promotion logos and links with an animated marquee feature With Pipeline's Logo list, you can easily build a section with brand logos or promotional images and add them to your shop:

Animated the images with a scrolling marquee option:

### Section settings Configure an optional heading, background color, marquee scrolling option, and padding options:

Logos are displayed on multiple rows based on the number of logo blocks used. To align all in one row, use fewer logo blocks or enable the animated marquee option to scroll on a single line. ### Block settings Add logos or images in the block settings. Use the link option to add a page link or external URL. If checked, *Open in new window* will open the link in a new tab or window. Adjust image sizing and padding with the control sliders:

**If no link URL is provided, there will be no call to action**

> ***Tip***: Use transparent .PNG images for best results. Alternatively, match the background color with the logo backgrounds. --- # 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/logo-list.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.