Merge branch 'main' into W-21112167-Replications-API

Author: charithaT07

docs/cli/content.md

@@ -1,26 +1,27 @@
 ---
-description: Commands for exporting and listing Page Designer content from B2C Commerce content libraries.
+description: Commands for exporting, listing, and validating Page Designer content from B2C Commerce content libraries.
 ---
 
 # Content Commands
 
-Commands for working with Page Designer content libraries on B2C Commerce instances.
+Commands for working with Page Designer content libraries and metadefinitions.
 
 ## Authentication
 
-Content commands require OAuth authentication:
+The `content export` and `content list` commands require OAuth authentication:
 
 | Operation | Auth Required |
 |-----------|--------------|
 | `content export` | OAuth (OCAPI for export job + WebDAV for assets) |
 | `content list` | OAuth (OCAPI for export job) |
+| `content validate` | None (local file validation) |
 
 ```bash
 export SFCC_CLIENT_ID=your-client-id
 export SFCC_CLIENT_SECRET=your-client-secret
 ```
 
-Both commands also support a `--library-file` flag for offline use with a local XML file, which skips authentication entirely.
+The `content export` and `content list` commands also support a `--library-file` flag for offline use with a local XML file, which skips authentication entirely.
 
 For complete setup instructions, see the [Authentication Guide](/guide/authentication).
 
@@ -201,3 +202,96 @@ footer-content (CONTENT ASSET)
 Pages show `id (typeId: type)`, components show `typeId (id)`, content assets show `id (CONTENT ASSET)`, and static assets show `path (STATIC ASSET)`. The tree uses color when output to a terminal: page names are bold, component type IDs are cyan, asset paths are green, and tree connectors are dim.
 
 With `--json`, returns `{ data: [...] }` with each item containing `id`, `type`, `typeId`, and `children` count.
+
+---
+
+## b2c content validate
+
+Validate Page Designer metadefinition JSON files against bundled JSON schemas. This is a local-only command — no instance connection or authentication is required.
+
+The command auto-detects the schema type using file path conventions (`experience/pages/` → pagetype, `experience/components/` → componenttype) and falls back to inspecting the JSON properties. You can also specify the type explicitly with `--type`.
+
+### Usage
+
+```bash
+b2c content validate <files...>
+```
+
+### Arguments
+
+| Argument | Description | Required |
+|----------|-------------|----------|
+| `files` | One or more file paths, directories, or glob patterns | Yes |
+
+When a directory is passed, all `*.json` files within it are validated recursively.
+
+### Flags
+
+In addition to [global flags](./index#global-flags):
+
+| Flag | Description | Default |
+|------|-------------|---------|
+| `--type`, `-t` | Schema type to validate against (skips auto-detection) | Auto-detected |
+
+Available schema types: `pagetype`, `componenttype`, `aspecttype`, `cmsrecord`, `customeditortype`, `contentassetpageconfig`, `contentassetcomponentconfig`, `contentassetstructuredcontentdata`, `image`.
+
+### Examples
+
+```bash
+# Validate a single page type definition
+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
+
+# Validate multiple files
+b2c content validate pages/home.json pages/about.json components/hero.json
+
+# JSON output for CI/scripting
+b2c content validate cartridge/experience/ --json
+```
+
+### Output
+
+The command prints a color-coded result for each file:
+
+```
+PASS: experience/pages/storePage.json (pagetype)
+PASS: experience/components/hero.json (componenttype)
+FAIL: experience/components/broken.json (componenttype)
+  ERROR at .attribute_definition_groups[0]: is required
+
+2/3 file(s) valid, 1 error(s)
+```
+
+The command exits with a non-zero status when any file fails validation.
+
+With `--json`, returns a structured result:
+
+```json
+{
+  "results": [
+    {
+      "valid": true,
+      "schemaType": "pagetype",
+      "errors": [],
+      "filePath": "/path/to/storePage.json"
+    }
+  ],
+  "totalFiles": 1,
+  "validFiles": 1,
+  "totalErrors": 0
+}
+```
+
+### Notes
+
+- Auto-detection uses file path conventions first: files under `experience/pages/` are validated as `pagetype`, files under `experience/components/` as `componenttype`. For other schema types, use `--type`.
+- Schemas are bundled with the SDK and follow the [Page Designer metadefinition specification](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/b2c-page-designer.html).
+- Use `b2c content validate` in CI pipelines to catch metadefinition errors before deployment.

docs/guide/third-party-plugins.md

@@ -1,5 +1,5 @@
 ---
-description: Community plugins for the B2C CLI including IntelliJ SFCC config integration and macOS Keychain credential storage.
+description: Community plugins for the B2C CLI including IntelliJ SFCC config integration, credential storage, docs search, catalog reduction, and pipeline visualization.
 ---
 
 # 3rd Party Plugins
@@ -185,6 +185,107 @@ b2c code deploy
 b2c code deploy
 ```
 
+### Docs Viewer Plugin
+
+**Repository:** [taurgis/b2c-plugin-docs-viewer](https://github.com/taurgis/b2c-plugin-docs-viewer)
+
+Searches Salesforce Help and fetches Help or Developer docs content directly from the CLI. This is useful when you want to look up platform documentation without leaving your terminal.
+
+#### Installation
+
+```bash
+b2c plugins install b2c-plugin-help-docs-viewer
+```
+
+If Playwright Chromium is not installed yet:
+
+```bash
+npx playwright install chromium
+```
+
+#### Features
+
+- Searches Salesforce Help with boxed, column-aligned results
+- Fetches Help or Developer docs pages by URL or by ID from the latest search
+- Fetches search results and article content in one command
+- Reuses cached results for up to 5 days, with `--no-cache` to bypass caching
+- Supports JSON output and optional raw extracted HTML
+
+#### Usage
+
+```bash
+# Search Salesforce Help
+b2c docs search-help-site "b2c commerce roles" --limit 5
+
+# Fetch an article by URL or by search result ID
+b2c docs help-site-article "https://help.salesforce.com/s/articleView?id=cc.b2c_roles_and_permissions.htm&type=5"
+b2c docs help-site-article 2
+
+# Search and fetch details in one step
+b2c docs fetch-results-help-site "pipelines" --limit 3
+```
+
+### Catalog Reducer Plugin
+
+**Repository:** [taurgis/b2c-plugin-catalog-reducer](https://github.com/taurgis/b2c-plugin-catalog-reducer)
+
+Generates smaller, representative Salesforce B2C Commerce catalog datasets from large source XML files. This is useful for creating fixtures, benchmarks, and reduced datasets for local development.
+
+#### Installation
+
+```bash
+b2c plugins install b2c-plugin-catalog-reducer
+```
+
+#### Features
+
+- Reduces large catalog XML files into smaller fixture datasets
+- Supports preferred product IDs, master-product targets, attribute-driven selection, and filler products
+- Writes catalog, inventory, and pricebook outputs in one run
+- Supports source-derived storefront catalogs and generated or source-derived pricebooks
+- Validates generated XML against bundled catalog, inventory, and pricebook schemas
+
+#### Usage
+
+```bash
+# Reduce a catalog using a custom config file
+b2c catalog reduce -i ./catalog.xml -o ./catalog-reduced.xml -c ./catalog-reducer.json
+```
+
+The reducer writes the reduced catalog plus derived inventory and pricebook XML outputs. Relative paths in `pricebookSourceFiles` and `storefrontSourceFiles` are resolved from the config file location.
+
+### Pipeline Visualizer Plugin
+
+**Repository:** [taurgis/b2c-plugin-pipeline-visualizer](https://github.com/taurgis/b2c-plugin-pipeline-visualizer)
+
+Generates ASCII and SVG previews of SFCC pipeline XML files. This is useful for inspecting pipeline structure, branch flow, and layout without opening Business Manager.
+
+#### Installation
+
+```bash
+b2c plugins install b2c-plugin-pipeline-visualizer
+```
+
+#### Features
+
+- Exports ASCII previews from pipeline XML files
+- Generates SVG image output for rendered pipeline layouts
+- Supports branch filtering for focused views
+- Can include grids, node lists, edge lists, and bendpoint details
+- Uses the same layout and edge routing logic across ASCII and SVG output
+
+#### Usage
+
+```bash
+# Export an ASCII view
+b2c pipeline ascii path/to/pipeline.xml --out debug/layouts/pipeline.txt
+
+# Export an SVG image
+b2c pipeline image path/to/pipeline.xml --out debug/layouts/pipeline.svg
+```
+
+Output is written to the file specified by `--out`.
+
 ## Creating Your Own Plugin
 
 Want to create a plugin? See the [Extending the CLI](./extending) guide for documentation on:

docs/typedoc.json

@@ -7,6 +7,7 @@
     "../packages/b2c-tooling-sdk/src/instance/index.ts",
     "../packages/b2c-tooling-sdk/src/logging/index.ts",
     "../packages/b2c-tooling-sdk/src/operations/code/index.ts",
+    "../packages/b2c-tooling-sdk/src/operations/content/index.ts",
     "../packages/b2c-tooling-sdk/src/operations/cip/index.ts",
     "../packages/b2c-tooling-sdk/src/operations/jobs/index.ts",
     "../packages/b2c-tooling-sdk/src/operations/logs/index.ts",

packages/b2c-cli/CHANGELOG.md

@@ -1,5 +1,16 @@
 # @salesforce/b2c-cli
 
+## 0.10.0
+
+### Minor Changes
+
+- [#278](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/pull/278) [`8c31081`](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/commit/8c31081b47e57e6a21e62425e6f19da036fc3e34) - Add `content validate` command to validate Page Designer metadefinition JSON files against bundled schemas. Supports auto-detection of schema types from file paths and content, or explicit `--type` flag. Includes glob pattern support for validating multiple files. (Thanks [@clavery](https://github.com/clavery)!)
+
+### Patch Changes
+
+- Updated dependencies [[`8c31081`](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/commit/8c31081b47e57e6a21e62425e6f19da036fc3e34), [`e4b5094`](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/commit/e4b5094d9c1c2a60e1214bc236ce7ed84c5d158b)]:
+  - @salesforce/b2c-tooling-sdk@0.11.0
+
 ## 0.9.0
 
 ### Minor Changes

packages/b2c-cli/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/b2c-cli",
   "description": "A Salesforce B2C Commerce CLI",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "author": "Charles Lavery",
   "bin": {
     "b2c": "./bin/run.js"
@@ -105,7 +105,7 @@
         "description": "Deploy and manage code versions on instances\n\nDocs: https://salesforcecommercecloud.github.io/b2c-developer-tooling/cli/code.html"
       },
       "content": {
-        "description": "Export and manage Page Designer content libraries"
+        "description": "Export, list, and validate Page Designer content"
       },
       "cip": {
         "description": "Run CIP analytics SQL and curated reports\n\nDocs: https://salesforcecommercecloud.github.io/b2c-developer-tooling/cli/cip.html"