@sleekcms/sync 1.4.0 → 1.4.2

package/dist/AGENT.md

@@ -57,6 +57,7 @@ Examples:
 /content/entries/<key+>.json       Content for a collection entry (array of objects; <key>+ matches the model filename)
 
 /content/images.json                       Site-level reusable images (handle → shortcut)
+/content/videos.json                       Site-level videos (handle → embed_url) — READ-ONLY, populated by UI uploads
 ```
 
 > **Tailwind**: Creating `/css/tailwind.css` enables Tailwind. It is compiled and injected automatically — do NOT add it via `link()`.
@@ -268,7 +269,7 @@ Model fields declare both the editor type and the shape expected in content JSON
 | `datetime` | ISO 8601 string |
 | `time` | `"HH:mm"` string |
 | `image` | Either a resolved `{ "url": "...", "alt": "..." }` object, **or** a shortcut string `"<source>:<search>"` (e.g., `"pexels:doctor"`, `"url:https://picsum.photos/200.jpg"`, `"cms:logo"`). Supported sources: `unsplash`, `pexels`, `pixabay`, `iconify`, `url`, `cms` (reuses an image declared in `/images.json` by handle). Append `\|<alt text>` to set the image's alt, e.g. `"pexels:doctor\|Smiling doctor with stethoscope"`. On save, the sync engine resolves the shortcut/link to a full image object automatically. |
-| `video` | Object of shape `{ "source": "BUNNY", "video_id": "...", "embed_url": "...", "title": "..." }`. **Do not write or invent this value.** Video uploads are user-driven in the CMS UI — the user uploads to Bunny.net and the sync engine stores the resolved object. In templates, always render videos with the `embed()` helper (e.g. `<%- embed(item.intro_video, { size: '1280x720' }) %>`), never by hand-rolling an iframe. |
+| `video` | Object of shape `{ "source": "BUNNY", "video_id": "...", "embed_url": "...", "title": "..." }`. **Do not write or invent this value.** Video uploads are user-driven in the CMS UI — the user uploads to Bunny.net and the sync engine stores the resolved object. In templates, always render videos with the `embed()` helper (e.g. `<%- embed(item.intro_video, { size: '1280x720' }) %>`), never by hand-rolling an iframe. The site's available video handles are exposed read-only at `/content/videos.json` (`handle → embed_url`) — look them up in templates with `getVideo('<handle>')`. |
 | `file` | Object of shape `{ "name": "...", "url": "...", "size": 0, "type": "...", "ext": "..." }` describing a downloadable document (PDF, CSV, DOC/DOCX, XLS/XLSX, PPT/PPTX, TSV, TXT — max 10 MB). **Do not write or invent this value.** File uploads are user-driven in the CMS UI — the user attaches the file via the editor and the sync engine stores the resolved object. In templates, render a link with `item.file.url` (download URL on `files.sleekcms.com`) and `item.file.name` (display name), e.g. `<a href="<%= item.brochure.url %>" download><%= item.brochure.name %></a>`. |
 | `json` | Object or array |
 | `sheet` | Array of arrays |
@@ -404,6 +405,23 @@ For images used in more than one place (logos, recurring icons, hero art), decla
 
 Then reference any of them from any content `image` field with `"cms:<handle>"` (e.g., `"cms:logo"`). The sync engine resolves it to the full image object on save. Templates can also fetch the resolved object directly via `getImage('<handle>')`.
 
+### Site videos (`/videos.json`) — READ-ONLY
+
+`/content/videos.json` is a flat map of `handle → embed_url` describing every video the user has uploaded to this site via the CMS UI (Bunny.net):
+
+```json
+{
+    "intro": "https://iframe.mediadelivery.net/embed/<lib>/<guid>",
+    "testimonial-jane": "https://iframe.mediadelivery.net/embed/<lib>/<guid>"
+}
+```
+
+**Do not edit `/content/videos.json`.** It is regenerated from the user's uploads — local edits will not sync and will be overwritten on the next pull. Use it only to discover which video handles are available, then fetch the resolved video object inside templates with `getVideo('<handle>')` and render it via `embed()`:
+
+```ejs
+<%- embed(getVideo('intro'), { size: '1280x720' }) %>
+```
+
 ---
 
 ## EJS Templates
@@ -444,6 +462,7 @@ Page records include: `item._path`, `item._slug` (collections), `item._meta.upda
 | `getEntry(handle)` | Object \| Array | Entry by handle. Single → object, collection → array |
 | `getSlugs(path)` | string[] | Slugs under a collection path |
 | `getImage(name)` | Object \| undefined | Site-level image by handle |
+| `getVideo(name)` | Object \| undefined | Site-level video by handle (handles listed in `/content/videos.json`, read-only) |
 | `getOptions(name)` | Array \| undefined | Option set as `[{ label, value }]` |
 | `getContent(query?)` | Any | Full content payload, or filter with JMESPath |
 | `path(page)` | String | URL path of a page object |
@@ -710,3 +729,5 @@ Template:
 16. **Collection pages whose model qualifies as "markdown content" — page model, collection (key ends with `+`), exactly one top-level `markdown` field, no `richtext` or `stack` anywhere — are stored as `.md` files with JSON frontmatter at `content/pages/<key+>/<slug>.md` (not `.json`).** All non-markdown fields go into the JSON frontmatter object between the `---` markers; the single `markdown` field's value is the body. When creating or editing such a record, prefer `.md`; the server also accepts `.json` for the same model. Inside the `.md` file, frontmatter may be written as JSON (canonical), JSON5 (trailing commas, `//` or `/* */` comments, unquoted keys), or YAML — all three are parsed correctly on save. Pulls always re-emit JSON as the canonical form.
 17. Always create RSS feed for blogs and link them in meta so it is discoverable. Use "rss.xml" as the key.
 18. Make the sites extremely SEO friendly and sharing friendly.
+19. When naming files for models, use - (dash) as word separator. Don't use _ (underscore) as it is mapped to / (slash) in path
+

package/dist/watcher.js

@@ -18,7 +18,7 @@ exports.stopWatching = stopWatching;
 const path_1 = __importDefault(require("path"));
 const chokidar_1 = __importDefault(require("chokidar"));
 const DEBOUNCE_DELAY = 5000;
-const IDLE_TIMEOUT_MS = 30 * 60 * 1000;
+const IDLE_TIMEOUT_MS = 60 * 60 * 1000;
 // Poll on a short interval and compare wall-clock time so the timeout still
 // fires correctly after the system has been asleep (Node's setTimeout runs on
 // a monotonic clock that pauses during sleep).

package/package.json

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