> 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/app-builder-components/welcome.md).
# Welcome
Ready made components you drag onto a Lightning page and configure right in the App Builder. Nothing to compose, nothing to code.
Install the ComponentsQuickstartExplore all components
An Avonni Data Table on an account record page, reading opportunities live.
***
Start here
Three pages, in order, and you have an Avonni component live on a Lightning page.
:rocket:
Quickstart Guide
Add your first Avonni component to a Lightning page, start to finish.
Point a component at an object, pick the fields, and it queries your records itself. No canvas to compose, no flow to build. Six of them below, each photographed on a Lightning page.
Cover image
Data Table
Filter, search and edit records inline, right on the page. Here, the opportunities behind an account.
{% hint style="info" %}
Need something these components do not do out of the box? **AX - Dynamic Component** puts a component you composed yourself on the same page. [Which one to pick](/app-builder-components/getting-started/choosing-between-app-builder-and-dynamic-components.md).
{% endhint %}
***
See it built
Projects built end to end in a real org, with the screenshots and the configuration behind each one.
Cover image
Richer record pages
Panels, timelines, catalogs and threads that live on the record page itself.
---
# 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/app-builder-components/welcome.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.
