> 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/experience-cloud/getting-started/quick-start-guide.md).

# Quick Start Guide

{% hint style="warning" %}

#### Before you install

Enable **Lightning Web Security** at the org level first: **Setup** > **Session Settings** > **Use Lightning Web Security for Lightning web components**.

With that setting off, the package installation fails during validation with `LWC1503: Dynamic imports are not allowed`. Nothing is wrong with the package or with your org: enable the setting and run the installation again.
{% endhint %}

{% hint style="warning" %}

#### Important

Before using Avonni Components on your Experience Cloud website, ensure that you activate the '**Lightning Web Security**' option. This toggle is in the settings panel under the '**Security & Privacy**' section. The Avonni Components may not function correctly if this setting is not enabled.

<img src="https://2929066058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDL6JQuZArjJeQvX2ot4y%2Fuploads%2Fgit-blob-21433c7e9f732551e3142fcb2d2972a134c244af%2F2023-11-13_14-21-22.png?alt=media" alt="" data-size="original">
{% endhint %}

## Accessing the Avonni Components

After installing the [**Avonni Experience Components package**](https://appexchange.salesforce.com/appxListingDetail?listingId=2e584bb3-b5e0-415d-9347-d6567158d840\&channel=recommended\&cta=gin\&other_source=AppExchange+Recommended), you can find and use these components in your Experience Cloud site editor:

### **Find the Components**

1. Open your Experience Site in Experience Builder
2. Click the **Components** panel (usually in the left sidebar)
3. Scroll to the **Custom Components** section
4. Look for components starting with "AX -" (like AX - Data Table, AX - Calendar, AX - Kanban)

### **Add Components to Your Page**

Once you find the AX components in the Custom Components list, simply drag and drop them onto your page canvas. Then configure the component's settings in the properties panel on the right.

All AX components for Experience Sites are prefixed with "AX -" to make them easy to identify and distinguish from standard Salesforce components.

<figure><img src="https://2929066058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDL6JQuZArjJeQvX2ot4y%2Fuploads%2Fgit-blob-3984a1c581d90c9ab96ec33f3860bdf262fb769e%2F2023-11-30_15-54-35.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}

#### Note

If you previously installed the Avonni Components package for Screen Flow, be aware that Experience Sites components use a different naming format:

* **Experience Sites components:** AX - Component Name (e.g., AX - Kanban, AX - Data Table)
* **Screen Flow components:** Avonni - Component Name (e.g., Avonni Kanban, Avonni Data Table)

Both can coexist in your org.
{% endhint %}

Once installed, the Avonni Components are available in your Experience Site editor. Next step: assign the licenses and permission sets your users need, on the License Management page.


---

# 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/experience-cloud/getting-started/quick-start-guide.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.