integrating-b2b-commerce-open-code-components

To integrate open-source B2B Commerce LWC components, the skill clones the forcedotcom repository, resolves the active package directory, and copies the LWC and label assets directly into your store's digitalExperiences site metadata paths.

No, manual cloning is not required. The skill automatically clones the repository into a temporary directory when needed, and it will even re-clone if the local directory structure is unexpected or invalid.

Custom labels might be missing if they were not copied into the correct digitalExperiences paths. This skill specifically copies sfdc_cms__label sets alongside sfdc_cms__lwc assets to ensure components render properly in Experience Builder.

The best way to populate the component palette is to push the LWC assets into the site metadata. This skill copies the open-source LWC files into the active package directory's digitalExperiences/site folder for immediate Experience Builder consumption.

If local store metadata is unavailable, the skill attempts to retrieve DigitalExperienceBundle site metadata from a connected Salesforce org, and falls back to creating a new store if the metadata cannot be retrieved.

No, an sfdx-project.json file is required. The skill relies on resolving the active package directory from this file to determine where to copy the LWC and label assets for your store.