B2c Content

B2C Content Skill

Use the b2c CLI to export, list, and validate Page Designer content from Salesforce B2C Commerce content libraries.

> Tip: If b2c is not installed globally, use npx @salesforce/b2c-cli instead (e.g., npx @salesforce/b2c-cli content export homepage).

Configuration & Authentication

The CLI auto-discovers the target instance and credentials from SFCC_* environment variables, dw.json in the current or parent directories, ~/.mobify, package.json, and configuration plugins. Flags like --server, --client-id, --client-secret, --username, and --password are usually unnecessary — only pass them to override what's auto-detected.

Run b2c setup inspect to see the resolved configuration and which source provided each value (use --json for scripting, --unmask to reveal secrets). For precedence rules and troubleshooting, see the b2c-cli:b2c-config skill.

Examples

Export Pages

# export a single page from a shared library
b2c content export homepage --library SharedLibrary

# export multiple pages
b2c content export homepage about-us contact --library SharedLibrary

# export pages matching a regex pattern
b2c content export "hero-.*" --library SharedLibrary --regex

# export to a specific output directory
b2c content export homepage --library SharedLibrary -o ./my-export

# export a specific component by ID
b2c content export hero-banner --library SharedLibrary

# export from a site-private library
b2c content export homepage --library RefArch --site-library

# preview without downloading (dry run)
b2c content export homepage --library SharedLibrary --dry-run

# export with JSON output
b2c content export homepage --library SharedLibrary --json

# export from a local XML file (offline, no instance needed)
b2c content export homepage --library SharedLibrary --library-file ./library.xml --offline

# filter pages by folder classification
b2c content export homepage --library SharedLibrary --folder seasonal

# custom asset extraction paths
b2c content export homepage --library SharedLibrary -q "image.path" -q "video.url"

# include orphan components in export
b2c content export homepage --library SharedLibrary --keep-orphans

List Content

# list all content in a library
b2c content list --library SharedLibrary

# list only pages
b2c content list --library SharedLibrary --type page

# list including components
b2c content list --library SharedLibrary --components

# show tree structure
b2c content list --library SharedLibrary --tree

# list from a site-private library
b2c content list --library RefArch --site-library

# list from a local XML file
b2c content list --library SharedLibrary --library-file ./library.xml

# JSON output
b2c content list --library SharedLibrary --json

Configuration

The --library flag can be configured in dw.json or package.json so you don't need to pass it every time:

// dw.json
{
  "hostname": "my-sandbox.demandware.net",
  "content-library": "SharedLibrary"
}

// package.json
{
  "b2c": {
    "contentLibrary": "SharedLibrary"
  }
}

With a configured library, commands become shorter:

b2c content export homepage
b2c content list --type page

Validate Metadefinitions

# validate a single metadefinition file
b2c content validate cartridge/experience/pages/storePage.json

# validate all metadefinitions in a directory recursively
b2c content validate cartridge/experience/

# validate with a glob pattern
b2c content validate 'cartridge/experience/**/*.json'

# explicitly specify the schema type
b2c content validate --type componenttype mycomponent.json

# JSON output for CI/scripting
b2c content validate cartridge/experience/ --json

Schema types are auto-detected from file paths (experience/pages/ → pagetype, experience/components/ → componenttype) and from JSON content. Use --type to override.

More Commands

See b2c content --help for a full list of available commands and options in the content topic.

Troubleshooting

• "Library is required" -- Set --library flag or configure content-library in dw.json.
• Authentication errors -- OAuth credentials are required for remote operations. Run b2c auth:login first. The --library-file flag bypasses authentication for offline/local use.
• Library not found -- Verify the library ID matches exactly. For site-private libraries, add --site-library.
• No content found -- Check that the page/content IDs exist. Use b2c content list to discover available IDs.
• Timeout errors -- Large libraries may exceed the default timeout. Use --timeout to increase it.

Related Skills

• b2c-cli:b2c-site-import-export - Site archive import/export operations
• b2c-cli:b2c-webdav - Low-level file operations on content libraries
• b2c-cli:b2c-config - Configuration and credential management

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: SalesforceCommerceCloud
• Source: SalesforceCommerceCloud/b2c-developer-tooling
• License: Apache-2.0
• Homepage: https://salesforcecommercecloud.github.io/b2c-developer-tooling/

Install and usage instructions live in the source repository linked above.