> 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/icon-columns.md). # Icon columns Build icon-based sections with a full set of included SVG commerce icons Promote your business advantages with easy-to-build high-resolution SVG icons:

Choose and customize from a rich set of commerce icons or use your own images for a custom icon:

Stacked or Slider options for mobile devices:

### Section settings Use the section settings to design the layout style, icon size, and icon placement:

### Block settings Each icon column block can be configured with a built-in icon, optional .PNG custom image, icon color, description text, and link:

Use the section settings for the layout style and block settings for each individual icon details:

--- # 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/icon-columns.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.