> 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/lwc-components/readme.md).

# Introduction

Welcome to the documentation for the **Avonni LWC Components** — a library of Lightning Web Components you use directly in your own LWCs to build rich Salesforce interfaces faster. Reference any component as an `avonni-*` tag in your component's HTML template and configure it through its attributes.

The library is split into two families:

* **Core Components** — 43 base UI building blocks: avatars, badges, cards, carousels, color/date/icon/visual pickers, combobox, sliders, progress indicators, media players, layout, and more. Drop them into any Lightning Web Component as presentational building blocks.
* **Data Driven Components** — 12 data-aware components: data table, kanban, scheduler, pivot table, timeline, tree, map, list, image list, carousel, and chat. Point them at a SOQL query (or static data) and they render, filter, sort, search, and paginate automatically.

Every component page documents what it does, its attributes and events, and includes copy-paste code examples.

## Getting started

* [Product Tour](/lwc-components/getting-started/product-tour.md) — what the library is, who it's for, and how it fits AI-assisted development.
* [Installation & Licenses Management](/lwc-components/getting-started/installation-and-licenses-management.md) — install the package from AppExchange and assign licenses.

Then browse the [Core Components](/lwc-components/core-components/core-components.md) and [Data Driven Components](/lwc-components/data-driven-components/data-driven-components.md) references.


---

# 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/lwc-components/readme.md?ask=<question>&goal=<endgoal>
```

`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.