docs: use idiomatic library/site IDs in libraries examples

The site library example now uses SiteGenesis (a real site ID) and the
shared library is RefArchSharedLibrary so the difference between a
site-private and shared library is obvious from the IDs alone.

Author: clavery

.changeset/site-library-config-support.md

@@ -4,4 +4,4 @@
 'b2c-vs-extension': minor
 ---
 
-The `libraries` config field now accepts `{id, siteLibrary?}` objects in addition to bare strings (mixed forms allowed in the same array). This lets you mark site-private libraries in `dw.json` or `package.json` so `b2c content list` / `content export` can default `--site-library` based on which library you target, and the VS Code Content Libraries tree auto-loads every configured library on activation. To upgrade, optionally replace `"libraries": ["RefArch"]` with `"libraries": ["RefArch", {"id": "homepage", "siteLibrary": true}]`. The existing string-only form continues to work unchanged. Also adds `libraries`, `assetQuery`, and `realm` to the documented `package.json` allowed fields list (already supported in code).
+The `libraries` config field now accepts `{id, siteLibrary?}` objects in addition to bare strings (mixed forms allowed in the same array). This lets you mark site-private libraries in `dw.json` or `package.json` so `b2c content list` / `content export` can default `--site-library` based on which library you target, and the VS Code Content Libraries tree auto-loads every configured library on activation. To upgrade, optionally replace `"libraries": ["RefArchSharedLibrary"]` with `"libraries": ["RefArchSharedLibrary", {"id": "SiteGenesis", "siteLibrary": true}]`. The existing string-only form continues to work unchanged. Also adds `libraries`, `assetQuery`, and `realm` to the documented `package.json` allowed fields list (already supported in code).

docs/cli/content.md

@@ -103,9 +103,9 @@ export SFCC_CLIENT_ID=your-client-id
 export SFCC_CLIENT_SECRET=your-client-secret
 b2c content export homepage
 
-# With a libraries config entry (see below) marking "homepage" as site-private,
-# --site-library is inferred automatically:
-b2c content export homepage --library homepage
+# With a libraries config entry (see below) marking the site library as
+# site-private, --site-library is inferred automatically:
+b2c content export homepage --library SiteGenesis
 ```
 
 ### Configuring multiple libraries
@@ -116,8 +116,8 @@ Listing libraries under `b2c.libraries` in `package.json` (or `libraries` in `dw
 {
   "b2c": {
     "libraries": [
-      "RefArch",
-      { "id": "homepage", "siteLibrary": true }
+      "RefArchSharedLibrary",
+      { "id": "SiteGenesis", "siteLibrary": true }
     ]
   }
 }
@@ -126,14 +126,14 @@ Listing libraries under `b2c.libraries` in `package.json` (or `libraries` in `dw
 With this config:
 
 ```bash
-# Uses RefArch (first entry) as the default library
+# Uses RefArchSharedLibrary (first entry) as the default library
 b2c content export hero-banner
 
 # --site-library is inferred from the matching entry
-b2c content export homepage --library homepage
+b2c content export homepage --library SiteGenesis
 
 # Explicit flag still overrides the config
-b2c content export homepage --library homepage --no-site-library
+b2c content export homepage --library SiteGenesis --no-site-library
 ```
 
 ### Output
@@ -198,10 +198,10 @@ b2c content list --library SharedLibrary --tree
 # List from a site-private library
 b2c content list --library RefArch --site-library
 
-# With a libraries config entry marking "homepage" as site-private,
+# With a libraries config entry marking the site library as site-private,
 # --site-library is inferred automatically (see "b2c content export"
 # above for an example b2c.libraries config):
-b2c content list --library homepage
+b2c content list --library SiteGenesis
 
 # List from a local XML file
 b2c content list --library SharedLibrary --library-file ./library.xml

docs/guide/configuration.md

@@ -353,19 +353,19 @@ A bare string is treated as a shared library; an object can mark a library as si
 {
   "b2c": {
     "libraries": [
-      "RefArch",
-      { "id": "homepage", "siteLibrary": true }
+      "RefArchSharedLibrary",
+      { "id": "SiteGenesis", "siteLibrary": true }
     ]
   }
 }
 ```
 
 With this config:
 
-- `b2c content list --library homepage` calls the site-library API automatically (no need to pass `--site-library`).
-- `b2c content list --library RefArch` treats `RefArch` as a shared library.
+- `b2c content list --library SiteGenesis` calls the site-library API automatically (no need to pass `--site-library`); the library ID is the site ID.
+- `b2c content list --library RefArchSharedLibrary` treats `RefArchSharedLibrary` as a shared library.
 - `--site-library` / `--no-site-library` on the command line still wins over the config default.
-- The VS Code Content Libraries tree shows both entries on activation, with `homepage` marked `[site]`.
+- The VS Code Content Libraries tree shows both entries on activation, with `SiteGenesis` marked `[site]`.
 
 ### Resolution Priority