> 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/dynamic-components/component-builder/advanced-features/structure-panel.md). # Structure Panel ## **Overview** The Structure Panel is a panel that shows every component in your Dynamic Component as a nested list. Components are organized by their parent-child relationships, making it easy to see which components are inside containers, sections, or other parent components. ### **Why use it?** When you're building complex layouts with multiple nested components, your canvas can get crowded and hard to navigate. The Structure Panel gives you a clear bird's-eye view of your entire structure. You can quickly find and select any component—even ones that are buried deep inside containers or hidden behind other elements. *** ## **How to Use It** **Finding components:** Click on any component name in the tree to select it on the canvas. This is especially useful when you can't easily click on a component directly because it's small, overlapping with others, or nested inside something else. **Understanding structure:** The indentation in the tree shows you the nesting levels. Parent components appear on the left, and their children are indented underneath. This helps you understand how your layout is organized and where each component sits in the hierarchy. **Reorganizing your layout:** Use the tree to identify where components are placed and decide if you need to move them. *** ## **When It's Most Helpful** * You have multiple nested containers or sections * Your layout includes many components and it's hard to click the right one * You're trying to understand how someone else structured a component * You need to find a specific component quickly without hunting through the canvas --- # 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.avonnicomponents.com/dynamic-components/component-builder/advanced-features/structure-panel.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.