LWR Sites for Experience Cloud

LWR Sites for Experience Cloud
Get to Know the Template
Start Building Your LWR Site
Create an LWR Site
Create Custom Pages
Create Components for LWR Sites
Create Custom Layout Components
Set Up a Navigation Menu Using Apex
Publish Your LWR Site
Brand Your LWR Site
Create a Multilingual LWR Site
Add More Customizations
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Create Custom Pages

Because the Build Your Own (LWR) template provides only a few key default pages, you must create additional custom pages for your particular use case.

To create a custom page, open the Pages menu on the top toolbar in Experience Builder. Click New Page at the bottom of the Pages menu. See Create Custom Pages with Experience Builder in Salesforce Help.

Standard Pages

When creating custom pages, the Search standard page is available for the template and supports certain routes and URL parameters.

Apart from the Search standard page, all other preconfigured standard pages, such as Knowledge, Account Management, and Contact Support, are unsupported.

Note

Object Pages

Because the recommended solutions for record page componentsuse the User Interface API to retrieve data, create object pages only for Supported Objects in the User Interface API Developer Guide.

Unlike in Aura templates, there are no generic record pages. If you need record pages, you must create them for a specific object.

Note

Login Pages

To use the Login, Forgot Password, and Registration pages that come with the authenticated Build Your Own (LWR) template, ensure that your site is published. In the Login & Registration tab of the Administration workspace, select Experience Builder Page for each page. Enter main for the Login page (1), Forgot Password for the Forgot Password page (2), and Register for the Registration page (3).

Login page, Forgot Password Page, and Registration page selection.

Page Access & Authentication

As is the case with Aura sites, we send page metadata to the client for all routes in the site, including for guest user sessions.

For this template, URL parameter validation during navigation differs from Aura sites. For example, we don’t prevent a user from accessing a record route when they don’t have permission to access that object or that particular record. We also don’t validate that URL parameters correspond to valid existing data in the org.

It’s the responsibility of the components on the page and the APIs used to enforce correct user sharing rules when retrieving data. Therefore, don’t put sensitive information on a page unless the data comes from an API that implements user access rules.

Important