LWR Sites for Experience Cloud
jNewer Version Available
New Publishing Model
LWR sites take advantage of a new publishing paradigm, where components are frozen when
the site is published and served statically at runtime.
This new paradigm allows LWR sites to deliver components and data as efficiently as possible, but it also introduces some caveats and limitations when managing your site and writing components.
In Aura sites, Lightning components (both Lightning web components and Aura components) are
delivered dynamically. So when you update a custom component that’s currently used in an Aura
site, your component changes go live immediately without publishing the site. However, in LWR
sites, you must publish your site before any changes, such as bug fixes or new features, can
propagate to standard, custom, or managed components.
Which Features Are Affected?
This table explains which features are affected by the new publishing model.
| Feature | You must republish your LWR site... |
|---|---|
| Lightning web components | When:
Until you republish the site, it uses the version of the previously published component’s source code, which can cause issues at runtime. |
| Managed package components | When you upgrade components from a managed package that are already in your site.
Until you republish the site, it uses the version of the previously published component’s source code, which can cause issues at runtime. |
| Labels | When you update a custom label or want updated labels from Salesforce. |