@se-studio/project-build 1.0.127 → 1.0.129

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @se-studio/project-build
 
+## 1.0.129
+
+### Patch Changes
+
+- Version bump: patch for changed packages
+
+## 1.0.128
+
+### Patch Changes
+
+- Version bump: patch for changed packages
+
 ## 1.0.127
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/project-build",
-  "version": "1.0.127",
+  "version": "1.0.129",
   "description": "Build tools and management scripts for SE Studio projects",
   "repository": {
     "type": "git",
@@ -72,7 +72,7 @@
   "devDependencies": {
     "@types/chroma-js": "^3.1.2",
     "@types/node": "^22.19.17",
-    "typescript": "^6.0.2",
+    "typescript": "^6.0.3",
     "vitest": "^4.1.4"
   },
   "scripts": {

package/skills/contentful-cms/core/SKILL.md

@@ -96,6 +96,13 @@ cms-edit set @c0 preHeading "Featured"
 cms-edit set @c0 anchor "hero-section"
 ```
 
+**Bulk scalar updates** — set a field on multiple entries in one command:
+```bash
+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.
+
 **Entry link fields** (template, articleType, etc. — value is the linked entry ID):
 ```bash
 cms-edit set @c0 template 3I0HxGKbUd173wIpFCsbVr --link
@@ -659,6 +666,7 @@ cat page.json | cms-edit create from-json             # Pipe from stdin
     {
       "contentType": "component",
       "type": "HeroSimple",
+      "cmsLabel": "Hero — Protecting Your Child from Cyberbullying",
       "target": "content",
       "fields": {
         "heading": "Protecting Your Child from Cyberbullying",
@@ -673,11 +681,13 @@ cat page.json | cms-edit create from-json             # Pipe from stdin
     {
       "contentType": "collection",
       "type": "CardGrid",
+      "cmsLabel": "Related topics grid",
       "fields": { "heading": "Related topics" },
       "items": [
         {
           "contentType": "component",
           "type": "Card",
+          "cmsLabel": "Card — Screen Time",
           "fields": { "heading": "Screen Time" }
         },
         {
@@ -731,8 +741,10 @@ cat page.json | cms-edit create from-json             # Pipe from stdin
 **Key points:**
 - Any component entry in `components` or `items` may use `{ existingId }` to link an existing entry instead of creating a new one.
 - The same applies to `links` entries — use `{ existingId }` to attach an existing link entry.
-- `fields.body` (and any value containing newlines or Markdown syntax) is automatically converted to Contentful rich text.
+- `cmsLabel` sets the human-readable label shown in Contentful's entry list. Defaults to `type` or `contentType` if omitted. **Always set `cmsLabel` on components when a page has multiple instances of the same type** (e.g. three CTAs) — editors need to distinguish them.
+- String `fields` values are converted to Contentful rich text when they match the Markdown heuristic: contains `\n\n` or `**` or `_`, starts with `#`, starts with `- `, or starts with `> ` (blockquote with a space). **Plain single-line text with none of those patterns is not converted** — for RichText fields, add `\n\n` or a heading line, or use `cms-edit rtf` afterwards.
 - `target` sets which content array to use: `topContent`, `content` (default), or `bottomContent`.
+- Slugs must not have a trailing slash — `from-json` strips it with a warning, but avoid it in source JSON.
 - All entries are created as **drafts**. A human must publish in Contentful.
 - `--dry-run` prints the full plan without writing anything.