> 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/shop-the-look.md). # Shop the look Show your products in context. ### Setup The hardest part about a shop the look section is finding an image that wil work on both desktop and mobile. For this reason we included the option to upload two images and have two sets of "hotspot" dots.

If you choose to use a separate image or a different crop of the same image, you'll need to check the box to enable this feature and upload a second image.

If you use a separate mobile image, make sure to set the dot position for both the desktop and mobile image. If you don't have a mobile image, the dot sliders for the mobile image no longer have any effect on the section.

I recommend placing the dot in a position where it's unlikely to be underneath the product card.

Mobile cards will open in a popup drawer. #### --- # 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/shop-the-look.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.