Experience Builder is reached from an existing Experience Cloud site, so you create the site first, then open it in the builder to customize pages, theme, and components.
- Create or open the site
In Setup, go to Digital Experiences then All Sites. Create a new site with a template (an LWR template for new builds) or click Builder next to an existing site to open it in Experience Builder.
- Set the theme and branding
Open the Theme panel and set colors, fonts, the logo, and component styling. Save a branding set if the site needs more than one look.
- Build pages and add components
Use the Pages menu to add or edit pages, then drag components from the palette onto the canvas and configure each one in the right-hand property panel.
- Configure navigation and audiences
Set up navigation menus and link each item to a page, object, or URL. Create audiences and assign them to page variations or components for personalization.
- Preview and publish
Use Preview to check the experience as different audiences, then click Publish to push the draft live. Visitors see the published version, not your in-progress drafts.
The runtime behind the template. LWR is the modern default for new sites; Aura supports both Aura and Lightning Web Components but is the legacy path.
Site-wide colors, fonts, logo, and component styling, optionally saved as switchable branding sets for multi-brand or seasonal sites.
Criteria that decide which visitors see a page variation, component, or branding set, based on authentication, profile, location, or field values.
One or more menus mapping labels to internal pages, objects, or external links, assignable per audience.
- The framework is chosen at site creation and cannot be swapped later without rebuilding, so decide LWR versus Aura before you start.
- Edits stay in draft until you click Publish; forgetting to publish is the most common reason a change does not appear on the live site.
- Stacking many audience-targeting rules per component makes a page hard to reason about; keep the rules few and documented.
- Custom Lightning Web Components only appear in the palette after they are configured for Experience Builder and deployed to the org.
Keep the related term in your library so you can find this topic again.