@salesforce/afv-skills 1.5.3 → 1.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/generating-experience-lwr-site/SKILL.md +1 -2
  3. package/skills/generating-experience-lwr-site/docs/configure-content-themeLayout.md +8 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@salesforce/afv-skills",
3
- "version": "1.5.3",
3
+ "version": "1.6.0",
4
4
  "description": "Salesforce skills for Agentforce Vibes",
5
5
  "license": "CC-BY-NC-4.0",
6
6
  "files": [
package/skills/generating-experience-lwr-site/SKILL.md CHANGED
@@ -145,8 +145,7 @@ Before doing anything, you **MUST ALWAYS** load them first if they match user in
145
145
 
146
146
  **Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
147
147
 
148
- - [ ] Check with user whether this new theme layout reuses an existing theme layout component or requires a new one.
149
- - [ ] MUST read [handle-ui-components.md](docs/handle-ui-components.md) if creating a new theme layout component.
148
+ - [ ] **CRITICAL**:Before doing anything else, MUST Check with user whether this new theme layout reuses an existing theme layout Lightning web component or requires a new one. If it requires a new one, make sure to read [handle-ui-components.md](docs/handle-ui-components.md) to create the new theme layout component before proceeding. DO NOT skip this step even if doing so would be faster or more efficient.
150
149
  - [ ] MUST read [configure-content-themeLayout.md](docs/configure-content-themeLayout.md).
151
150
  - [ ] MUST read [configure-content-view.md](docs/configure-content-view.md) if need to apply theme layout to pages
152
151
 
package/skills/generating-experience-lwr-site/docs/configure-content-themeLayout.md CHANGED
@@ -26,6 +26,9 @@
26
26
 
27
27
  **IMPORTANT**: These guidelines should ONLY be applied when the user explicitly requests creating a new layout for their site. Do not apply these guidelines automatically for other tasks or when editing existing layouts.
28
28
 
29
+ ### Order of operations
30
+ If the user decides to create a new LWC, create the LWC first THEN the theme layout metadata.
31
+
29
32
  ### _meta.json Structure
30
33
 
31
34
  The `_meta.json` file must contain:
@@ -126,11 +129,11 @@ digitalExperiences/site/[SITE_NAME]/sfdc_cms__theme/[THEME_API_NAME]/content.jso
126
129
 
127
130
  When generating a new theme layout, ensure:
128
131
 
129
- - [ ] `_meta.json` created with correct `apiName`, `type`, and `path` (III)
130
- - [ ] `content.json` created with all required fields (IV)
131
- - [ ] `urlName` uses lowercase with hyphens (V)
132
- - [ ] `title` is human-readable (V)
133
- - [ ] `sfdc_cms__theme/[THEME_API_NAME]/content.json` updated by appending a new `contentBody.layouts` mapping (VI)
132
+ - [ ] `_meta.json` created with correct `apiName`, `type`, and `path`
133
+ - [ ] `content.json` created with all required fields
134
+ - [ ] `urlName` uses lowercase with hyphens
135
+ - [ ] `title` is human-readable
136
+ - [ ] `sfdc_cms__theme/[THEME_API_NAME]/content.json` updated by appending a new `contentBody.layouts` mapping
134
137
  - [ ] **CRITICAL**: Complete all the UUID generation steps. See [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md)
135
138
 
136
139
  ## Purpose B: Editing Existing Theme Layouts