> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/websites/product-categorisation/product-variants/category-list-page.md). # Category List Page Let’s say you’ve created variant groups for a particular T-Shirt style. The garment is available in Black, White and Green and sizes S,M and L for each colour. You chose *not* to include colour as a variant attribute, so you created 3 variant groups: * Snazzy T-Shirt, Green * Snazzy T-Shirt, Black * Snazzy T-Shirt, White Again, colour could have been a variant attribute, but in this case, you chose to present colours separately. Later, you’ll set up ‘Related Groups’ to cross-sell colours! Each of these variant groups will look like a single product in category list displays, so you create a parent category called ‘Snazzy T-Shirts’ and assign this as the parent category on each of the above variant groups. The result is that when a customer views the ‘Snazzy T-Shirts’ category, they will see 3 “products” (which we know are actually variant groups, not individual products). Seeing as we want the customer to see which sizes are available for each colour, we also choose check the ‘Show Variants’ option on each of the variant groups. Obviously customers can’t purchase variant groups - they need to actually decide which concrete product to add to their cart. Therefore, instead of an ‘Add To Cart’ button on the category page, they will see a ‘Select Variant’ button (you can customise this text). > If there are pricing differences amongst members of the variant group, they will also see a price range instead of a specific price. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pakk.io/websites/product-categorisation/product-variants/category-list-page.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.