> 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/welcome.md).
# Welcome
Over forty components for Experience Cloud sites: branded layouts, data components and interactions, for the people who are not in your org.
Install the ComponentsQuickstartBuild with AI
A partner portal, built from Avonni components on an Experience site.
***
Start here
Three pages, in order, and you have an Avonni component running on a site page.
:rocket:
Quick Start Guide
Add your first Avonni component to an Experience Site page, start to finish.
{% hint style="info" %}
The components run on **Aura and LWR sites**. In Aura sites, [slots](/experience-cloud/getting-started/learning-the-basics.md#understanding-slots) are not available.
{% endhint %}
How the palette colour codes a component
* **Content components (green icon)** present your message: text, media, and the blocks around them.
* **Layout components (blue icon)** set the structure of the page, so functionality and aesthetics work together.
* **Data components (purple icon)** display and interact with your data.
* **Other components (red icon)** cover the specialized cases that do not fit the three above.
***
Build it with an AI assistant
Describe the page you want in plain language. Your assistant looks up the real component catalog through the Avonni MCP server, then builds it.
:wand-magic-sparkles:
Setup
Install the Avonni Skills and connect the MCP server to your assistant, once.
To contact us directly, email .
---
# 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/experience-cloud/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.
