> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/broadcast-v5/sections/broadcast-sections/shop-the-look.md). # Shop the look Shoppers can find products from branded images Broadcast's interactive image and product section helps shoppers find the products from your brand images.

### Flexible Use it as a static image to promote products. Or display the product dots, which link to the products, making it easier to find the right one. Perfect for any page, including Lookbooks. The product dots can be easily positioned over the branded image and link to the product in the section. ### Customize * For desktop viewers, position the brand image on the left or right side. * Products can be shown in one or two columns. * Toggle the product dots to make it an interactive or static section. * Each product block has horizontal and vertical dot position sliders to map precisely where you like. * Mobile users have an interactive slider to view the products:

### Video Overview This video demonstrates the section settings and block options for the **Shop the Look** section, including mobile layouts: {% embed url="" %} **Shop the look section video overview** {% endembed %} --- # 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://broadcast.presidiocreative.com/broadcast-v5/sections/broadcast-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.