b2c-content
Export, list, and validate Page Designer content from B2C Commerce libraries. Use this skill whenever the user needs to export Page Designer pages or components, list pages in a content library, validate page JSON or metadefinitions, discover page IDs, migrate content between instances, or work with library XML offline. Also use when extracting content for review or building content deployment pipelines -- even if they just say 'export the homepage' or 'what pages are in the shared library'.
What this skill does
# 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`).
## 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
```
### Validate Metadefinitions
```bash
# 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 <seconds>` 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
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.