> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/vertical-visual-picker/adding-sub-items.md).
# Adding sub-items
## Overview
One of the most powerful features of the Vertical Visual Picker is the ability to add sub-items. This allows you to create a hierarchical list of items, which can be very helpful for organizing large amounts of data. For example, you could create a vertical visual picker for a product catalog, where each parent item could represent a category of products, and the sub-items could represent individual products.
## How to add sub-items
Adding sub-items to the Vertical Visual Picker is easy.
1. Drag the Vertical Visual Picker component
2. Open the Component Builder
3. Add your items in the Data Source section
4. Scroll down to the sub-items sections to add your sub-items
---
# 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://docs.avonnicomponents.com/flow/tutorials/components/vertical-visual-picker/adding-sub-items.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.
