@se-studio/contentful-cms 2.8.2 → 3.0.1

package/docs/help/person-from-json.md

@@ -3,8 +3,8 @@
 `create person-from-json` creates multiple `person` entries from a single JSON file. Use it for spreadsheet-to-CMS author imports and team directory bootstraps.
 
 ```bash
-cms-edit create person-from-json --file authors.json --dry-run
-cms-edit create person-from-json --file authors.json --if-not-exists
+cms-edit create person-from-json --json '{...}' --dry-run
+cms-edit create person-from-json --json '{...}' --if-not-exists
 ```
 
 All entries are created as **drafts**. Nothing is published automatically.

package/docs/help/taxonomy-from-json.md

@@ -3,8 +3,8 @@
 `create taxonomy-from-json` creates multiple `tagType`, `articleType`, and `tag` entries from a single JSON file. It is the recommended way to bootstrap taxonomy for import scripts and publication workflows.
 
 ```bash
-cms-edit create taxonomy-from-json --file taxonomy.json --dry-run
-cms-edit create taxonomy-from-json --file taxonomy.json --if-not-exists
+cms-edit create taxonomy-from-json --json '{...}' --dry-run
+cms-edit create taxonomy-from-json --json '{...}' --if-not-exists
 ```
 
 Processing order: **tagTypes → articleTypes → tags** (tags depend on tagTypes).
@@ -65,7 +65,7 @@ Top-level link shorthands (`templateId`, `featuredImageId`, `topContentIds`, etc
 
 | Option | Description |
 |---|---|
-| `--file <path>` | Path to taxonomy JSON (required) |
+| `--json <json> or --json-base64 <encoded>` | Path to taxonomy JSON (required) |
 | `--if-not-exists` | Skip creation when slug already exists; return existing ID |
 | `--dry-run` | Validate all entries and link targets without writing |
 
@@ -73,7 +73,7 @@ Top-level link shorthands (`templateId`, `featuredImageId`, `topContentIds`, etc
 
 ## Output
 
-Human mode prints a summary per entry. JSON mode (`CMS_EDIT_JSON=1` or `--json`):
+Human mode prints a summary per entry. JSON mode (`CMS_EDIT_JSON=1` or `--json-output`):
 
 ```json
 {
@@ -92,7 +92,7 @@ Combine batch bootstrap with `create … --if-not-exists` and `resolve` for scri
 
 ```bash
 # One-time taxonomy bootstrap
-cms-edit create taxonomy-from-json --file taxonomy.json --if-not-exists
+cms-edit create taxonomy-from-json --json '{...}' --if-not-exists
 
 # Look up IDs in scripts
 cms-edit resolve --tag-type-slug presentation-type --json

package/docs/help/workflow.md

@@ -78,7 +78,7 @@ cms-edit set @c2 backgroundColour "Navy"
 cms-edit rtf @c2 body "## Overview\n\nFirst paragraph.\n\nSecond paragraph."
 
 # From a file (long content)
-cms-edit rtf @c2 body --file content/body.md
+cms-edit rtf @c2 body --content "# ..."
 ```
 
 ### Multi-value: replacing inline content

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/contentful-cms",
-  "version": "2.8.2",
+  "version": "3.0.1",
   "description": "CLI tool for AI agents to read and edit Contentful draft content without publish permissions",
   "repository": {
     "type": "git",

package/skills/core/SKILL.md

@@ -120,7 +120,7 @@ cms-edit set @c0 anchor "hero-section"
 cms-edit set @c1:cmsLabel="Hero — School avoidance" @c2:cmsLabel="What is school avoidance?" @c3:cmsLabel="Signs of school avoidance"
 cms-edit set @c1:heading="Title A" @c2:heading="Title B"
 ```
-Each token is `@ref:fieldName=value`. All values are scalar (string, boolean, number). Flags like `--link`, `--links`, `--file` do not apply in multi mode.
+Each token is `@ref:fieldName=value`. All values are scalar (string, boolean, number). Flags like `--link`, `--links`, `--json` do not apply in multi mode.
 
 **Entry link fields** (template, articleType, etc. — value is the linked entry ID):
 ```bash
@@ -158,7 +158,7 @@ For any content with multiple paragraphs or newlines, use `printf` piped to stdi
 printf '## Why it matters\n\nOur platform helps teams **move faster**.\n\n- Instant setup\n- No code required\n' | cms-edit rtf @c1 body --markdown -
 
 # Also correct — file input
-cms-edit rtf @c1 body --markdown --file path/to/file.md
+cms-edit rtf @c1 body --markdown --content "# Heading\n\nBody."
 cms-edit rtf @c1 body --markdown - < path/to/file.md
 ```
 
@@ -170,7 +170,7 @@ cms-edit rtf @c1 body --markdown "Simple single-paragraph body text with **bold*
 
 **Surgical rich text replace** (compliance / quidget tokens — does not re-import the whole field):
 
-- Matching is **per Contentful text node** only. If the author split a phrase with bold (e.g. `**Annual fee: **$95`), the string `Annual fee: $95` will **not** match as one piece; use a shorter `--find` or full `rtf … --file`.
+- Matching is **per Contentful text node** only. If the author split a phrase with bold (e.g. `**Annual fee: **$95`), the string `Annual fee: $95` will **not** match as one piece; use a shorter `--find` or full `rtf … --content`.
 - Quidget strings contain `*`, which Markdown would treat as italic — use **`--replace-plain`**, not `--replace`.
 
 ```bash
@@ -246,7 +246,7 @@ Same as Component plus:
 When adding body content and a CTA (e.g. PDF download) to an article:
 
 1. `cms-edit open --article-slug <slug>` (or `open --id <id>`)
-2. Set body: `cms-edit rtf @<ref> body --markdown "..."` or `--markdown --file path/to.md`. If you need to add a body component first, use `add` then `rtf`.
+2. Set body: `cms-edit rtf @<ref> body --markdown "..."` or `--content` / `--base64`. If you need to add a body component first, use `add` then `rtf`.
 3. `cms-edit add CTA --target bottomContent`
 4. Set CTA links: use `--type external --label "Download PDF" --href <url>` for an external PDF URL, or `--type download --label "Download PDF" --asset-id <asset-id>` for a Contentful asset (get the ID from `cms-edit asset search "..."` or `asset info <id>`).
 5. `cms-edit save`
@@ -430,10 +430,10 @@ cms-edit create tag --slug easl-congress-2026 --name "EASL Congress 2026" --tag-
   --description "Research presented at EASL Congress 2026." --featured-image <logoAssetId>
 
 # Full fields via JSON
-cms-edit create tag --json-file tag.json --tag-type presentation-type --if-not-exists
+cms-edit create tag --json '{"slug":"presentation"}' --tag-type presentation-type --if-not-exists
 
 # Batch bootstrap
-cms-edit create taxonomy-from-json --file taxonomy.json --if-not-exists
+cms-edit create taxonomy-from-json --json '{"tagTypes":[...]}' --if-not-exists
 
 # Idempotent single-entry creates
 cms-edit create tag-type --slug conference-venue --name "Conference Venue" --if-not-exists
@@ -664,9 +664,9 @@ cms-edit peek --id <entryId>         # Look up by entry ID
 Run a sequence of operations from a JSON file or stdin.
 
 ```bash
-cms-edit batch run --file ops.json            # Run batch ops from file
+cms-edit batch run --json '[...]'            # Run batch ops from inline JSON
 echo '[...]' | cms-edit batch run             # Pipe from stdin
-cms-edit batch run --file ops.json --dry-run  # Validate without saving
+cms-edit batch run --json '[...]' --dry-run  # Validate without saving
 ```
 
 Supported ops: `open`, `set`, `rtf`, `rtf-replace`, `save`, `add`, `links-add`.
@@ -700,8 +700,8 @@ Example `ops.json` — update an existing page with a new CTA that has two butto
 Create a complete page or article — including all components, fields, and CTA links — from a single declarative JSON file. This is the recommended approach for creating multiple pages or articles in bulk.
 
 ```bash
-cms-edit create from-json --file page.json            # Create from file
-cms-edit create from-json --file page.json --dry-run  # Preview without writing
+cms-edit create from-json --json '{...}'            # Create from inline JSON
+cms-edit create from-json --json '{...}' --dry-run  # Preview without writing
 cat page.json | cms-edit create from-json             # Pipe from stdin
 ```