Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/experience-cloud-site-setup

experience-cloud-site-setup

Verified

Use 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.

templates/experience-cloud-site-setup-template.md

View on GitHub
# Experience Cloud Site Setup — Work Template

Use this template when creating or reviewing an Experience Cloud site configuration.

## Scope

**Skill:** `experience-cloud-site-setup`

**Request summary:** (fill in what the user asked for)

**Org:** (org name / sandbox name)

**Date:** (fill in)

---

## Pre-Creation Checklist

Complete this section before creating the site. These decisions cannot be undone after site creation.

### Edition and Licensing

- [ ] Org edition confirmed: Enterprise / Performance / Unlimited / Developer (circle one)
- [ ] Experience Cloud licenses provisioned (if applicable)
- [ ] Partner Community or Customer Community licenses allocated (if applicable)

### Component Inventory

List all components that will be used on this site:

| Component Name | Type (LWC / Aura) | Existing or New | Compatible with LWR? |
|---|---|---|---|
| (fill in) | | | |
| (fill in) | | | |
| (fill in) | | | |

- [ ] All components are LWC-only → LWR template is viable
- [ ] One or more Aura components that cannot be migrated → Aura template required (document reason below)

**Reason for Aura template (if applicable):** ___

### Template Selection Decision

- [ ] **Build Your Own (LWR)** — greenfield, all LWC, performance-critical
- [ ] **Microsite (LWR)** — small public-facing site, minimal pages
- [ ] **Partner Central** — standard partner workflows (deal registration, lead sharing)
- [ ] **Customer Account Portal** — standard customer self-service (cases, accounts)
- [ ] **Build Your Own (Aura)** — Aura component dependency documented above

**Rationale:** ___

### URL Path

- Site URL path (set at creation, permanent): `/___`
- Full URL will be: `MyDomainName.my.site.com/___`
- [ ] My Domain is deployed in this org
- [ ] URL path confirmed with stakeholders

---

## Context Gathered

Record the answers to the Before Starting questions from SKILL.md here.

- Edition / licensing: ___
- Template selected: ___
- Component inventory complete: Yes / No
- My Domain deployed: Yes / No
- Custom domain requirement: ___
- Known constraints (Aura deps, timeline, etc.): ___

---

## Approach

Which pattern from SKILL.md applies? Why?

- [ ] New customer portal with LWR template
- [ ] Partner community with pre-built template
- [ ] Other: ___

**Justification:** ___

---

## Branding Configuration

For LWR sites (Branding Set tokens):

| Token | Value |
|---|---|
| `--dxp-color-brand` | |
| `--dxp-color-background` | |
| `--dxp-color-text-primary` | |
| `--dxp-font-family-primary` | |
| Logo URL / asset | |

For Aura sites (Theme Panel):

- Primary color: ___
- Secondary color: ___
- Font: ___
- Logo: ___

---

## Navigation Menu Structure

**Primary navigation:**

| Label | URL / Page | Visibility (Public / Authenticated / Profile) |
|---|---|---|
| (fill in) | | |
| (fill in) | | |
| (fill in) | | |

**Secondary / footer navigation (if applicable):**

| Label | URL / Page | Visibility |
|---|---|---|
| (fill in) | | |

---

## Page Inventory

| Page Name | URL Path | Template / Layout | Key Components |
|---|---|---|---|
| Home | / | (fill in) | |
| (fill in) | | | |
| (fill in) | | | |

---

## Post-Publish Validation Checklist

- [ ] Site published (not just saved) — confirmed publish timestamp updated
- [ ] Site URL resolves at `MyDomainName.my.site.com/path`
- [ ] Branding renders correctly (logo, colors, fonts)
- [ ] Navigation menus appear with correct items and visibility
- [ ] Pages load without errors (check browser console)
- [ ] Tested as unauthenticated guest user (incognito/private window)
- [ ] Tested as authenticated user
- [ ] Guest user profile permissions reviewed — no unnecessary object or field access
- [ ] HTTPS confirmed on all pages

---

## Notes

Record any deviations from the standard pattern and why.

___
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall