@sleekcms/sync 1.2.3 → 1.3.0

package/README.md

@@ -272,12 +272,14 @@ Models describe the shape of your content. They're JSON-like files with unquoted
 | `markdown` | Markdown string |
 | `number` | Number |
 | `boolean` | `true` / `false` |
+| `emoji` | Single Unicode emoji character, e.g. `"😀"` |
 | `date` | `YYYY-MM-DD` |
 | `image` | `{ url, alt }` |
 | `video` | `{ url, embed }` |
 | `link` | URL string |
 | `json` | Object or array |
 | `block(key)` | Embedded block object |
+| `stack` | Array of heterogeneous block objects; each item carries `_block: "<block_key>"` to name its block |
 | `entry(key)` | Entry object or slug reference |
 
 ---

package/dist/AGENT.md

@@ -188,6 +188,62 @@ Block models cannot contain other blocks. Use groups (`{ ... }`) or collections
 
 Repeatable blocks use the same collection syntax as groups and entries: `[block(cta)]`. Use this sparingly, only when each repeated item should use the same reusable block template. For simple one-page repeated content, prefer a repeating group (`[{ ... }]`). For reusable content selected across pages, prefer a collection entry plus `[entry(key)]`.
 
+### Stacks
+
+A **stack** is a heterogeneous list of blocks: each item picks its own block schema. Use a stack when a page section can contain a mix of different reusable components in an editor-chosen order. If every item would use the same block, prefer `[block(key)]` instead — stacks are for "section A could be a hero, a CTA, a quote, or a gallery."
+
+**Model syntax** — bare `stack`, no parentheses and no `[]`. Stacks are always multiple by definition:
+
+```
+{
+    title: text,
+    sections: stack
+}
+```
+
+Any block defined in `models/blocks/` may appear in any stack — the allowed set is the full block library, not a per-field allow-list.
+
+**Content shape** — an array of objects. Each item is shaped like the block model it uses, plus a `_block` marker naming that block by key (as a plain string):
+
+**`content/pages/about.json`**
+```json
+{
+    "title": "About us",
+    "sections": [
+        {
+            "_block": "hero",
+            "heading": "Care that feels personal",
+            "subheading": "A small team focused on long-term relationships.",
+            "background": "pexels:doctor"
+        },
+        {
+            "_block": "cta",
+            "label": "Book a visit",
+            "link": "/contact"
+        }
+    ]
+}
+```
+
+The `_block` value is the block's key (e.g., `"hero"`, `"cta"`) — never a numeric id. The CMS resolves it server-side on save.
+
+**Rendering** — each item flows through its own `blocks/<key>.ejs` template. Pass the whole array to `render()` and it dispatches per `_block`:
+
+**`pages/about.ejs`**
+```ejs
+<h1><%= item.title %></h1>
+<%- render(item.sections) %>
+```
+
+**Stack vs block vs collection** — same decision tree as blocks, with one extra rung:
+
+- One-off shape used on one page → group `{ ... }` or `[{ ... }]`.
+- Reusable shape, always the same per item → `block(key)` or `[block(key)]`.
+- Reusable shape, but items can be different blocks chosen by the editor → `stack`.
+- Shared content referenced from many pages → `entry(key)` / `[entry(key)]`.
+
+Like blocks, stacks cannot be nested inside block models. Stack items themselves may contain groups, collections, and entry references, but not other stacks or blocks.
+
 **Entry reference** — Use `entry(key)` for one, `[entry(key)]` for many:
 ```
 {
@@ -206,6 +262,7 @@ Model fields declare both the editor type and the shape expected in content JSON
 | `text`, `paragraph`, `richtext`, `markdown`, `code`, `color`, `link` | String |
 | `number` | Number |
 | `boolean` | `true` / `false` |
+| `emoji` | Single Unicode emoji character string, e.g. `"😀"` or `"👋🏽"` (one emoji per record; not free text) |
 | `date` | `"YYYY-MM-DD"` string |
 | `datetime` | ISO 8601 string |
 | `time` | `"HH:mm"` string |
@@ -216,6 +273,7 @@ Model fields declare both the editor type and the shape expected in content JSON
 | `location` | `{ "markers": [{ "lat": n, "lng": n }], "img": "..." }`; `img` is a Google Maps Static Image URL that already includes the markers and can include formatting parameters such as `size`, `zoom`, `scale`, `maptype`, and styling |
 | `block(key)` | Object matching that block's model; stored inline in the parent page/entry content and rendered with `blocks/<key>.ejs` |
 | `[block(key)]` | Array of block objects; each item matches the block model and renders with `blocks/<key>.ejs` |
+| `stack` | Array of heterogeneous block-shaped objects. Each item is `{ "_block": "<block_key>", ...fields_of_that_block }`. `_block` is the target block's key as a plain string; the remaining keys must match that block's model. Different items in the same stack may use different blocks. Stored inline; each item renders through its own `blocks/<key>.ejs`. The CMS resolves block keys to ids server-side — never write numeric ids. |
 | `entry(key)` / `[entry(key)]` | Slug string / array of slug strings in content JSON; entry object / array of entry objects in templates |
 | Group `{ ... }` | Nested object |
 | Collection `[{ ... }]` | Array of nested objects |

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@sleekcms/sync",
-    "version": "1.2.3",
+    "version": "1.3.0",
     "description": "Edit SleekCMS sites locally — models, content, templates, images — with live two-way sync and AI agent support.",
     "keywords": [
         "sleekcms",