layer-groupOverview

The Avonni Components App is the management hub inside Salesforce where you organize, version, and deploy your Dynamic Components. The Component Builder is where you build them; the Components App is where you keep them tidy, control which version is live, and manage your library as it grows.


Builder vs. App

Two distinct surfaces with two distinct jobs.

Component Builder
Avonni Components App

What it is

A visual canvas for designing components.

A Salesforce app for managing them.

Where you find it

Opens when you click into a component.

Salesforce App Launcher → "Avonni Dynamic Components".

Use it for

Drag-and-drop, configure properties, wire up data and interactions.

Versioning, folders, deployment, cloning, sharing.

Output

A configured component definition.

A live, deployed component available on Lightning Pages.


Open the App

In Salesforce, click the App Launcher (9-dot waffle icon, top-left), search for Avonni Experience Components, and open it. The app lands on the component list view, showing every Dynamic Component in your org.

circle-info

Pin the app to your Salesforce navigation bar to skip the App Launcher each time. Click the dropdown arrow next to the app name and select Add to Nav Bar


Manage Component Versions

Every Dynamic Component carries a version history. New versions let you experiment without breaking what's already live, roll back if something goes wrong, and track how a component evolved over time.

Action
What it does

New Version

Creates an editable copy from the current active version. The active version stays live for end users while you work.

Activate

Promotes a version to live. Lightning Pages start using it on next load.

View History

Lists every version with its created date and author. Click any version to inspect or clone it.

Deactivate

Takes the active version offline. Use sparingly — pages embedding the component will break.

→ Working with Versions — full workflow with screenshots

Organize with Folders

Folders let you group components by team, project, or use case. Good folder hygiene becomes essential once you pass a dozen or so components.

Action
What it does

Create Folder

Spins up a new folder from the list view. Name it for the team, the page, or the use case it serves.

Move Component

Drag any component into a folder, or use the row action menu.

Nested Folders

Organize folders inside folders for finer structure (e.g., SalesPipeline Dashboards).

→ Folder Management — full setup and best practices

Where to go next

Page
What's on it

Tour of the visual design environment where components are built.

Step-by-step on creating, activating, and rolling back versions.

How to set up and maintain a folder structure as your library grows.

Pushing a component live to a Lightning Page or Experience Site.


Last updated

Was this helpful?