home / skills / salesforcecommercecloud / b2c-developer-tooling / b2c-content

b2c-content skill

safe

This skill helps you export and list Page Designer content from Salesforce B2C Commerce libraries, enabling asset discovery and page ID retrieval for

npx playbooks add skill salesforcecommercecloud/b2c-developer-tooling --skill b2c-content

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.1 KB

---
name: b2c-content
description: Export and list Page Designer pages from B2C Commerce content libraries. Use when exporting pages with components and assets, discovering page IDs, or working with content library XML.
---

# B2C Content Skill

Use the `b2c` CLI to export and list 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`).

## Examples

### Export Pages

```bash
# 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

```bash
# 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:

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

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

With a configured library, commands become shorter:

```bash
b2c content export homepage
b2c content list --type page
```

### More Commands

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

## 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

Overview

This skill exports and lists Page Designer pages and their assets from Salesforce B2C Commerce content libraries using the b2c CLI. It helps discover page IDs, extract components and media, and work with content library XML for offline or scripted workflows. Use it to streamline page exports, previews, and targeted asset extraction for migrations or deployments.

How this skill works

The skill wraps b2c content commands to fetch pages, components, and assets from a configured content library or a local library XML file. It supports exact names, regex matching, folder filters, dry-run previews, and JSON output for automation. You can export whole pages, specific components by ID, or list content trees and components for discovery.

When to use it

You need to export Page Designer pages and their component assets for backup or migration.
You want to discover page IDs, component relationships, or folder classification in a library.
You need to preview what will be exported without downloading (dry run).
You are automating content exports and want machine-readable JSON output.
You need to work offline from a local content library XML file or integrate with CI scripts.

Best practices

Configure the default content library in dw.json or package.json to avoid repeating the --library flag.
Use --dry-run first to verify matching pages or regex patterns before downloading assets.
Prefer JSON output for scripting and CI integration; parse results to drive further automation.
When migrating, include --keep-orphans to capture components that are not referenced by pages.
Validate exported assets and component paths with custom queries (-q) to ensure required fields are extracted.

Example use cases

Export the homepage and hero components from the shared library for local editing and testing.
List all pages and components in a site-private library to audit content structure before a release.
Run a regex export to grab all seasonal hero banners for a campaign deployment.
Use a local library XML file in an offline environment to extract pages without an instance connection.
Integrate content export into CI to produce JSON manifests used by deployment pipelines.

FAQ

What if b2c is not installed globally?

Use npx @salesforce/b2c-cli followed by content commands to run the CLI without global installation.

Can I export components only or limit which asset fields are saved?

Yes—export specific components by ID and use -q queries to extract custom asset paths or fields.