@W-21482430 feat: migrate exp lwr site knowledge docs to skill#27
@W-21482430 feat: migrate exp lwr site knowledge docs to skill#27hsinghbisht-sfdc merged 29 commits intoforcedotcom:mainfrom
Conversation
skills/salesforce-experience-lwr-site/docs/configure-content-view.md
Outdated
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/configuring-guest-sharing-rules.md
Outdated
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/handle-ui-components.md
Outdated
Show resolved
Hide resolved
| - **keyPrefix**: 3-character identifier unique to each standard object (Account=001, Contact=003) | ||
| - **ObjectApiName**: Custom object API name including the "__c" suffix | ||
|
|
||
| Obtain object information from the `objectList` output: |
There was a problem hiding this comment.
Since the objectList + knowledge are no longer together in one response - do you see any issues of this instruction referencing the output from the IA? Just wondering
skills/salesforce-experience-lwr-site/docs/configure-content-themeLayout.md
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/configure-content-view.md
Outdated
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/configure-content-themeLayout.md
Outdated
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/configure-content-view.md
Outdated
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/configure-content-view.md
Outdated
Show resolved
Hide resolved
skills/salesforce-experience-lwr-site/docs/configure-content-themeLayout.md
Outdated
Show resolved
Hide resolved
|
|
||
| - `type`: Always `"sfdc_cms__view"` | ||
| - `title`: Human-readable display title (e.g., About Us) | ||
| - `contentBody`: Include all `required` properties from `schemaDefinition`. Use `examplesOfContentType` for reference. |
There was a problem hiding this comment.
With skills do we get this schemaDefinition?
There was a problem hiding this comment.
It will be from MCP. That's why I mentioned we still need MCP.
There was a problem hiding this comment.
It will still call execute_metadata_action from the top level skills file https://github.com/forcedotcom/afv-library/pull/27/changes#diff-5f4c96f675183da24ccbe5ad3beca61ce5987eb1b06907d9d287c8f801a979c4
feat: handle component slots
|
Thanks for the contribution! It looks like @jeffcarey is an internal user so signing the CLA is not required. However, we need to confirm this. |
| @@ -0,0 +1,196 @@ | |||
| --- | |||
| name: salesforce-experience-lwr-site | |||
There was a problem hiding this comment.
Please follow the recommended naming recommendation for skills
Just to follow consistent pattern which we are about to do for all other existing type is generating* i.e. generating-experience-lwr-site
There was a problem hiding this comment.
Since this PR is old, going ahead with merge, we will track this change as part of PR #53
Migrated knowledge docs from Expert Framework MCP to skill.
Also made some changes to re-organize some of the sections and added TOC for longer knowledge docs based on https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices#structure-longer-reference-files-with-table-of-contents.
@W-21482430@