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 USER_MODE clause or the stripInaccessible method. To hide specific fields from a guest or external authenticated users, follow the sample code outlined below.