> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/sections/products.md). # Products Sections for featuring products, recommendations, and shoppable media. Sections for putting products front and center — featured picks, recommendations, and interactive shoppable layouts. * **Featured Products, Featured Collections & Featured Collection Grid** — hand-picked products or collections, shown as a grid or slider. * **Featured Product** — a block-based single-product info layout. * **Product with Text & Featured Collection with Media** — a product or collection paired with a large image or video. * **Product Recommendations & Recently Viewed Products** — automatic product suggestions, from Shopify's engine or the shopper's own browsing history. * **Shoppable Media Slider & Product Hotspots** — clickable, shoppable image and video layouts. * **Sticky Collection Grid** — a collection grid that stays pinned in view while scrolling. --- # 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://staylime.com/docs/volume-themes/sections/products.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.