Default for new sites: fast, LWC-native, full control of the layout
Microsite (LWR)
LWR
Marketing-style pages with little record data
Customer/Partner templates (Aura)
Aura
Only when a required standard component has no LWR equivalent. Name that component in the ADR and check the gap list each release
Help Center, Build Your Own (Aura)
Aura
Existing sites; migrate rather than extend
The standard-component gap is the whole decision. Before committing to LWR, list the standard components the site needs (record lists, case deflection, knowledge, CMS collections) and confirm each exists for LWR in the current release. Do that check once, in writing, rather than discovering it mid-build.
2. Licence decides the sharing mechanism
Licence
Sharing
Typical use
Customer Community
Sharing Sets and Share Groups (no roles)
High-volume B2C portals
Customer Community Plus
Roles, sharing rules, reports
B2B customers needing hierarchy or delegated admin
Partner Community
Roles, sharing rules, leads and opportunities
Channel partners working your pipeline
External Identity
Identity only
Sign-in and profile management, little record access
Consequence for the data model: a design built on sharing rules does not work for Customer Community users, who have no roles. Decide the licence with the data model (salesforce-data-model → references/sharing-model.md), not after the site is built.
3. Guest users
Everything a guest can reach is public. The guest user profile gets object and field access; records come only through guest sharing rules, which are capped and audited.
Guest-facing Apex is with sharing, always USER_MODE, and never without sharing. "Secure guest user record access" is on in modern orgs and should stay on.
Guest users cannot own records; anything a guest creates needs an owner assignment path (queue, flow, default owner).
Rate and abuse: a public form is an unauthenticated write endpoint. Add reCAPTCHA on the flow or the form, cap what one submission can create, and monitor volume.
Test as a guest in a private window. Testing while logged in proves nothing about guest access.
4. Branding and content
Theme Layouts (custom ones are LWCs with lightningCommunity__Theme_Layout) hold header, footer and navigation; pages stay layout-free.
Branding sets and SLDS 2 styling hooks carry colour and type; no per-component literals.
Audiences control component and page visibility by profile, record, or custom criteria — the supported way to vary a page without duplicating it.
Salesforce CMS for content that marketing edits; do not put marketing copy in component markup.
Custom domain, CSP Trusted Sites and CORS are configured before launch, not after the first broken third-party script.
5. Performance and SEO
Public pages are measured by Lighthouse and Core Web Vitals like any other site. The Community Page Optimizer is an Aura-site tool — for LWR use the browser's Lighthouse panel and field data.
Budget: keep the initial payload small, avoid a wire that fans out into several Apex calls, size and lazy-load images, and defer third-party scripts.
Server-side rendering with the lightning__ServerRenderable / lightning__ServerRenderableWithHydration capabilities is available for LWR components where first paint matters.
SEO: page titles and meta per page, a sitemap, clean URLs and comm__namedPage navigation so links are real URLs rather than client-side state.
Guest data through cacheable Apex where the result is the same for everyone; per-user data is never cached at the CDN.
6. Launch checklist
Template and runtime chosen with the standard-component gap list written down
Licence chosen with the sharing mechanism it implies
Guest profile and guest sharing rules reviewed; no without sharing in guest paths
Public forms rate-limited and captcha-protected; created records have an owner
Theme layout, branding set and audiences configured instead of duplicated pages
Custom domain, CSP Trusted Sites, CORS in place
Lighthouse budget met on the two most-visited public pages
SEO basics per page; navigation uses comm__namedPage
Tested as a guest, as an external user and as an internal user
# Experience Cloud — templates, licences, guest users, performance
Target: Spring '26. Sources: [Experience Cloud templates](https://help.salesforce.com/s/articleView?id=sf.exp_cloud_basics_which_template.htm&type=5), [LWR sites](https://developer.salesforce.com/docs/platform/lwr/guide/lwr-intro.html), [Secure guest user access](https://help.salesforce.com/s/articleView?id=sf.networks_guest_user_sharing_security.htm&type=5).
## 1. Template choice
| Template | Runtime | Use |
|---|---|---|
| **Build Your Own (LWR)** | LWR | Default for new sites: fast, LWC-native, full control of the layout |
| **Microsite (LWR)** | LWR | Marketing-style pages with little record data |
| **Customer/Partner templates (Aura)** | Aura | Only when a required standard component has no LWR equivalent. Name that component in the ADR and check the gap list each release |
| **Help Center, Build Your Own (Aura)** | Aura | Existing sites; migrate rather than extend |
The standard-component gap is the whole decision. Before committing to LWR, list the standard components the site needs (record lists, case deflection, knowledge, CMS collections) and confirm each exists for LWR in the current release. Do that check once, in writing, rather than discovering it mid-build.
## 2. Licence decides the sharing mechanism
| Licence | Sharing | Typical use |
|---|---|---|
| **Customer Community** | Sharing Sets and Share Groups (no roles) | High-volume B2C portals |
| **Customer Community Plus** | Roles, sharing rules, reports | B2B customers needing hierarchy or delegated admin |
| **Partner Community** | Roles, sharing rules, leads and opportunities | Channel partners working your pipeline |
| **External Identity** | Identity only | Sign-in and profile management, little record access |
Consequence for the data model: a design built on sharing rules does not work for Customer Community users, who have no roles. Decide the licence with the data model (`salesforce-data-model` → `references/sharing-model.md`), not after the site is built.
## 3. Guest users
- Everything a guest can reach is public. The guest user profile gets object and field access; records come only through **guest sharing rules**, which are capped and audited.
- Guest-facing Apex is `with sharing`, always `USER_MODE`, and never `without sharing`. "Secure guest user record access" is on in modern orgs and should stay on.
- Guest users cannot own records; anything a guest creates needs an owner assignment path (queue, flow, default owner).
- Rate and abuse: a public form is an unauthenticated write endpoint. Add reCAPTCHA on the flow or the form, cap what one submission can create, and monitor volume.
- Test as a guest in a private window. Testing while logged in proves nothing about guest access.
## 4. Branding and content
- **Theme Layouts** (custom ones are LWCs with `lightningCommunity__Theme_Layout`) hold header, footer and navigation; pages stay layout-free.
- Branding sets and SLDS 2 styling hooks carry colour and type; no per-component literals.
- **Audiences** control component and page visibility by profile, record, or custom criteria — the supported way to vary a page without duplicating it.
- Salesforce CMS for content that marketing edits; do not put marketing copy in component markup.
- Custom domain, CSP Trusted Sites and CORS are configured before launch, not after the first broken third-party script.
## 5. Performance and SEO
- Public pages are measured by Lighthouse and Core Web Vitals like any other site. The **Community Page Optimizer** is an Aura-site tool — for LWR use the browser's Lighthouse panel and field data.
- Budget: keep the initial payload small, avoid a wire that fans out into several Apex calls, size and lazy-load images, and defer third-party scripts.
- Server-side rendering with the `lightning__ServerRenderable` / `lightning__ServerRenderableWithHydration` capabilities is available for LWR components where first paint matters.
- SEO: page titles and meta per page, a sitemap, clean URLs and `comm__namedPage` navigation so links are real URLs rather than client-side state.
- Guest data through cacheable Apex where the result is the same for everyone; per-user data is never cached at the CDN.
## 6. Launch checklist
- [ ] Template and runtime chosen with the standard-component gap list written down
- [ ] Licence chosen with the sharing mechanism it implies
- [ ] Guest profile and guest sharing rules reviewed; no `without sharing` in guest paths
- [ ] Public forms rate-limited and captcha-protected; created records have an owner
- [ ] Theme layout, branding set and audiences configured instead of duplicated pages
- [ ] Custom domain, CSP Trusted Sites, CORS in place
- [ ] Lighthouse budget met on the two most-visited public pages
- [ ] SEO basics per page; navigation uses `comm__namedPage`
- [ ] Tested as a guest, as an external user and as an internal user