Experience Cloud Developer Guide
jSummer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Using the Developer Console
Configure Drag-and-Drop Aura Components for Experience Builder
Expose Component Attributes in Experience Builder
Tips and Considerations for Configuring Aura Components for Experience Builder
Supported Aura Components, Interfaces, and Events
Personalization Target Developer and Group Names
Comply with a User’s Personal Information Visibility Settings
Analyze and Improve Experience Builder Site Performance
Add Pardot Tracking to Your Experience Builder Site
Use a CMS with Your Experience Builder Site
Newer Version Available
Develop Experience Builder Sites: The Basics
Learn about the Developer Console development tool, how to create a basic drag-and-drop
Aura component, and tips to consider along the way.
-
Using the Developer Console
The Developer Console provides tools for developing your Aura components and applications. -
Configure Drag-and-Drop Aura Components for Experience Builder
Before you can use a custom Aura component in Experience Builder, there a few configuration steps to take. -
Expose Component Attributes in Experience Builder
You use a design resource to control which attributes are exposed in Experience Builder. A design resource lives in the same folder as your component. It describes the design-time behavior of the Aura component—information that visual tools need to display the component in a page or app. -
Tips and Considerations for Configuring Aura Components for Experience Builder
Keep these guidelines in mind when creating Aura components and component bundles for Aura sites. -
Supported Aura Components, Interfaces, and Events
Not all Aura components, interfaces, and events are supported for Aura-based Experience Builder sites. Some are available only for the Salesforce mobile app or Lightning Experience. Check out what’s available before customizing your site. -
Personalization Target Developer and Group Names
Determine the developer name and group name for your experience variation targets when using Connect REST API or Metadata API to personalize your Experience Builder site. -
Comply with a User’s Personal Information Visibility Settings
Orgs with portals and sites provide specific settings to hide a user’s personally identifiable and contact information from other users. These settings aren’t enforced in Apex, even with Apex security features such as the WITH SECURITY_ENFORCED clause or the stripInaccessible method. To hide specific fields from a guest or external authenticated users, follow the sample code outlined below.