> 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/projects/dynamic-components/overview.md). # Overview ## Building Basics Components


My Active Opportunities	Combine a Card, Data Table, and reactive Metrics to create a "My Active Opportunities" view.	Mastering the Avonni Dynamic Components Package (11).png	My Active Opportunities
Enhanced Related List	Replace standard lists with an Avonni Data Table, adding custom actions, advanced filters, search, and inline editing.	Mastering the Avonni Dynamic Components Package (12).png	Enhanced Related List
How to Use Avatars as Quick Links to Related Records	Learn how to use the Avonni Avatars link to related records in sidebar.	Mastering the Avonni Dynamic Components Package (16).png	How to Use Avatars as Quick Links to Related Records

## Working with Data


Related Contacts Card	This guide uses the Avonni List and Card components, demonstrating how to query and filter Contacts using the current Account's context.	Mastering the Avonni Dynamic Components Package (14).png	Related Contacts Card
User Activity Report	Learn how to use a Combobox to select a user and dynamically update Metrics, a Map of account locations, and a Data Table of activities.	Mastering the Avonni Dynamic Components Package (13).png	User Activity Report with Dynamic Components
Build a "Quick Lead" Entry Form	Learn to build a no-code quick lead form widget	Mastering the Avonni Dynamic Components Package (17).png	Build a "Quick Lead" Entry Form
How to Build a Record Edit Form for modals & panels	Learn to build a modal form that edits records	Mastering the Avonni Dynamic Components Package (18).png	How to Build a Record Edit Form for modals & panels

## Advanced Layouts & Interactions


Vertical Tabs with Reactive Data Table	Display Accounts in vertical tabs alongside a Data Table that automatically updates to show related Opportunities.	Mastering the Avonni Dynamic Components Package (10).png	Vertical Tabs with Reactive Data Table
Campaign Performance Dashboard	Learn to create a reusable component that lets users instantly switch between views of Leads Generated, Opportunities Created...	Mastering the Avonni Dynamic Components Package (9).png	Dynamic Tradeshow Campaign Performance Dashboard
Dynamic Opportunity Viewer	This tutorial shows how to use an Input Choice Set and Component Visibility rules to display only the selected view.	Mastering the Avonni Dynamic Components Package (8).png	Dynamic Opportunity Viewer
Build a Custom Record Header & Highlights Panel	Learn to design a custom no-code record page header	Mastering the Avonni Dynamic Components Package (15).png	Build a Custom Record Header & Highlights Panel

--- # 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/projects/dynamic-components/overview.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.