LWR Sites for Experience Cloud
Summer '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)
Create Custom Record Components
Use Apex and SOQL for Search
Use Expressions to Add Dynamic Data to LWR Sites
Create a Logout Link Component
Improve Performance with Experience Delivery
Add More Customizations
This section describes several advanced customizations, such as creating custom record
components and using Apex and SOQL for search.
-
Create Custom Record Components
The Build Your Own (LWR) template doesn’t include record components, but you can use the User Interface API to construct your own custom components. -
Use Apex and SOQL for Search
Create a theme layout search component that sends the user to a search results page. -
Use Expressions to Add Dynamic Data to LWR Sites
With expressions, you can make calculations and access property values and other data from Salesforce or content from Salesforce CMS to pass into a component’s attributes. Use expressions for dynamic output or for passing values into components by assigning them to attributes. -
Create a Logout Link Component
To log out your users, you can create a custom logout link component. -
Integrate Third-Party Libraries Using the Privileged Script Tag
Some components within an LWR site encapsulate their elements in shadow DOM, which prevents global interaction with those components. As a result, third-party JavaScript libraries such as Google Analytics and Google Tag Manager can have trouble querying the DOM globally on an LWR site. When programmatic access to an element within the DOM is needed, you can write scripts within an <x-oasis-script> privileged script tag. Loading third-party libraries using this privileged script tag lets those libraries bypass any shadow DOM boundaries.