PranavNagrecha/AwesomeSalesforceSkills / skills/admin/experience-cloud-site-setup
experience-cloud-site-setup
VerifiedUse when creating a new Experience Cloud site: selecting LWR vs Aura template, configuring branding and navigation, setting up a custom domain, and using Experience Builder. Trigger keywords: create new Experience Cloud site, LWR vs Aura template, set up community portal domain, Experience Builder page builder, branding sets, navigation menu configuration, Microsite LWR, Build Your Own LWR. NOT for coding LWR themes or custom components — use lwc/lwr-site-development. NOT for deploying a finished site to another org — use devops/experience-cloud-deployment-admin. Also covers the deployable metadata: Network, CustomSite, NavigationMenu, ExperienceBundle, DigitalExperienceBundle, urlPathPrefix, networkMemberGroups, emailSenderAddress, site status Live vs UnderConstruction.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 23.5 KB |
| references/examples.md | markdown | 7.1 KB |
| references/gotchas.md | markdown | 17.8 KB |
| references/llm-anti-patterns.md | markdown | 7.2 KB |
| references/metadata-examples.md | markdown | 21.9 KB |
| references/well-architected.md | markdown | 8.5 KB |
| scripts/check_experience_cloud_site_setup.pyexecutable | script | 21.2 KB |
| templates/experience-cloud-site-setup-template.md | markdown | 3.7 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — Experience Cloud Site Setup
## Relevant Pillars
- **Security** — Experience Cloud sites expose Salesforce data and functionality to external users, including unauthenticated guests. The guest user profile is the primary attack surface: it must be scoped to minimum necessary permissions. Object- and field-level security on the guest profile must be explicitly reviewed before go-live. Sharing settings determine which records partners or customers can see; overly permissive sharing (e.g., Public Read/Write on sensitive objects) can expose data to unintended audiences. Custom domains must be configured with HTTPS; Salesforce enforces HTTPS on `*.my.site.com` domains by default.
- **Performance Efficiency** — LWR templates deliver the primary performance advantage in Experience Cloud. Publish-time page freezing and HTTP caching at the CDN layer reduce per-request org compute significantly for high-traffic public sites. Using LWR for public-facing portals is the architecturally sound default. Choosing Aura for a high-traffic site sacrifices this caching layer.
- **Scalability** — For high-traffic sites, LWR's CDN caching model reduces load on Salesforce servers by serving cached pages for unauthenticated sessions. Authenticated sessions still hit Salesforce for data. For authenticated-heavy sites, consider data access patterns carefully (LDS wire adapters, caching within components) rather than relying solely on the template choice.
- **Reliability** — The publish model on LWR sites is a reliability consideration: changes do not propagate until explicitly published. A broken publish does not affect the currently serving version (the last published build remains live). This is a safety feature but also means practitioners must maintain an explicit publish workflow to avoid serving stale content.
- **Operational Excellence (metadata in source)** — A site whose settings live only in Setup cannot be reviewed or promoted. `Network`, `CustomSite`, `NavigationMenu` and the content bundle are all retrievable types; keeping them in version control is what makes the template decision, the membership shape and the publish status auditable. One caveat that shapes the practice: `emailSenderAddress` diverges between source and org after the first deploy by design, so a repo-vs-repo diff is not evidence about that one field.
- **Operational Excellence** — Documenting the template selection decision (LWR vs Aura) and the component inventory used to make it is critical for long-term maintainability. Template decisions cannot be reversed; undocumented choices lead to confusion when teams grow or ownership changes.
## Architectural Tradeoffs
**LWR vs Aura:** The LWR template is the strategic direction for Experience Cloud. It offers superior performance through publish-time caching, clean URL paths, and a modern component model (LWC-only). The tradeoff is that it requires all components to be LWC — any existing Aura component investment must be migrated or left behind. For greenfield projects, LWR is the correct default. For projects with significant Aura component debt, the Aura template may be necessary as a transitional choice, but teams should plan for eventual migration.
**Pre-built templates vs Build Your Own:** Pre-built templates (Partner Central, Customer Account Portal) deliver faster time to value for standard use cases at the cost of flexibility. Build Your Own (LWR or Aura) gives full control over page structure and component composition at the cost of more upfront build effort. The right choice depends on how closely the use case maps to the pre-built template's assumptions.
**Custom domain vs default site URL:** Using My Domain (`MyDomainName.my.site.com`) is the standard production pattern. Salesforce-hosted default URLs can be used for development but should not be the primary URL for a production site as they are harder to brand and may change.
## Anti-Patterns
1. **Creating a site with the wrong template and iterating on it** — Because template selection is permanent, starting with a quick "exploratory" site creation and then building on top of it is risky. If the template turns out to be wrong, everything built must be rebuilt. Always confirm the template decision before creating the site, even for a proof of concept. If a throwaway site is needed for exploration, name it clearly as temporary and delete it before the production site is created.
2. **Granting broad guest user permissions for speed** — Granting the guest user profile object-level read access to all standard objects, or enabling "View All" on the guest profile to quickly get pages rendering, is a security anti-pattern. This exposes sensitive Salesforce data to unauthenticated internet users. Scope guest user permissions to only the objects and fields genuinely required for public pages. Test explicitly as an unauthenticated user before go-live.
3. **Hardcoding styles in component CSS instead of using --dxp- tokens** — When LWC components embedded in LWR sites use hardcoded color values or font sizes in their CSS instead of consuming `--dxp-*` CSS custom property tokens, the components become disconnected from the site's branding set. A branding change in Experience Builder will not cascade to those components. All component styles for Experience Cloud should consume the relevant `--dxp-*` tokens so the branding system remains coherent.
## Official Sources Used
- LWR Sites for Experience Cloud (v66.0, Spring '26) — LWR vs Aura template comparison, publish model, performance behavior, LWR template limitations
- Salesforce Help: Custom Domain for Experience Cloud — Custom domain pattern (`MyDomainName.my.site.com`), My Domain requirement
- Salesforce Help: Experience Builder — Page builder, navigation menu configuration, branding sets, site publishing
- Salesforce Well-Architected Overview — Architecture quality framing (Security, Performance Efficiency pillars) — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
- Metadata API Developer Guide, `Network` (Summer '26 / v62, api_meta.txt L90671–L92035) — Required fields (`emailSenderAddress`, `emailSenderName`, `forgotPasswordTemplate`, `site`, `status`, `tabs`), the write-once behaviour of `emailSenderAddress` (L90784–L90795), the `Live` / `DownForMaintenance` / `UnderConstruction` status enum (L91054–L91074), `networkMemberGroups` and its Chatter-customer carve-out (L90963–L90970), `selfRegistration` / `selfRegProfile` (L91035–L91042), `urlPathPrefix` (L91084–L91089), `maxFileSizeKb` (L90936–L90941) — https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf
- Metadata API Developer Guide, `CustomSite` (api_meta.txt L46743–L47235) — the Security pillar's site-container controls: `clickjackProtectionLevel` values and the "(recommended)" annotation on `SameOriginOnly` (L46876–L46888), `requireHttps` removed in API 52.0 and ignored earlier (L47015–L47017), `redirectToCustomDomain` defaulting to `false` in Experience Cloud sites (L46982–L46989), `allowStandardPortalPages` as an access control (L46796–L46804), and `guestProfile` / `subdomain` being Read only (L46959, L47059)
- Metadata API Developer Guide, `NavigationMenu` and `NavigationMenuItem` (api_meta.txt L90445–L90668) — the five valid item types and their `target` rules (L90515–L90564), `publiclyAvailable` as a menu-visibility flag rather than a permission (L90509–L90510), and the note that Help Center and LWR templates ship no generic record pages (L90449–L90452)
- Metadata API Developer Guide, `ExperienceBundle` (api_meta.txt L59875–L61121), `DigitalExperienceBundle` (L51103–L51375) and `DigitalExperienceConfig` (L53950–L54050) — which bundle type applies to which site vintage and the packaging restriction on enhanced LWR (L51234–L51238), `brandingSetType` and the fixed `definitionName` values per standard template (L59996–L60019), the `SiteDotCom`-in-manifest exclusion (L61110), and the cross-API-version deploy sequence (L61111–L61115)
- Object Reference, `Network` and `NetworkMember` (Summer '26 / v62, object_reference.txt L186629–L188420) — Setup labels for the status values (Published / Offline / Preview) and the one-way nature of `UnderConstruction` (L187347–L187373), `UrlPathPrefix` carrying the `Update` property (L187375–L187378), and the supported calls on both objects that make membership a consequence rather than an insert (L186636–L186637, L188301–L188302) — https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |