@sleekcms/sync 4.4.0 → 4.5.0

package/README.md

@@ -420,7 +420,7 @@ Content lives in `src/content/` as plain JSON. Edit any content file and save
 
 ## Site setup (`src/setup.json`)
 
-Site-wide decisions made once — the default page title, whether Tailwind is compiled, whether a sitemap is published, the cookie consent switch, the chat bot switch, and analytics tag ids — live in `src/setup.json`, mirrored from **Settings → Website** in the CMS. The file is JSON with a comment above each key explaining it:
+Site-wide decisions made once — the default page title, whether Tailwind is compiled, whether a sitemap is published, the cookie consent switch, the chat bot switch and how the chat opens, and analytics tag ids — live in `src/setup.json`, mirrored from **Settings → Website** in the CMS. The file is JSON with a comment above each key explaining it:
 
 ```json5
 {
@@ -429,6 +429,7 @@ Site-wide decisions made once — the default page title, whether Tailwind is co
   sitemap_enabled: false,   // publish sitemap.xml + robots.txt on every build
   cookie_consent: false,    // consent banner; holds analytics + data-sleekcms-consent scripts until accepted
   chat_enabled: false,      // chat bot on every page, answering from the site's published pages
+  chat_mode: "POPUP",       // how the chat opens: "POPUP", "SIDEBAR" or "SPOTLIGHT" (any case accepted)
   analytics: {              // tag ids injected into every page; include only the ones you use
     ga4: "G-XXXXXXXXXX",
   },

package/dist/AGENTS.md

@@ -125,6 +125,7 @@ setup.json                      Site setup (JSON, comments allowed): default pag
 | `sitemap_enabled` | boolean | `true` publishes `sitemap.xml` + `robots.txt` on every build. Turn it on for public sites and SEO work. Which pages are *excluded* is a CMS UI setting (Manage Site > Search Visibility), never this file. |
 | `cookie_consent` | boolean | `true` injects a consent banner into every page and holds the analytics tags, plus any script or iframe tagged `data-sleekcms-consent`, until the visitor accepts its category. A toggle only — banner text, position and styling are authored in HTML (§14). |
 | `chat_enabled` | boolean | `true` adds the chat bot to every published page; it answers visitor questions from the site's published pages (re-read on every publish). A toggle only — the welcome message, knowledge files and instructions are managed in the CMS. `false` removes it from the next publish and stops open chats right away. |
+| `chat_mode` | string | How the chat opens when a visitor clicks its launcher: `"POPUP"` (default, a small panel in the corner), `"SIDEBAR"` (a full-height panel docked right, over the page) or `"SPOTLIGHT"` (a centred search-style dialog). Any case is accepted and saved uppercase. On phones sidebar and spotlight open full screen. Changes with the next publish. A page can override it: `data-sleek-chat="sidebar"` (or `"spotlight"`, `"popup"`) on any button or link opens chat in that mode, and `--sleek-chat-mode` in the site's CSS sets it per page or breakpoint. |
 | `analytics` | object | Marketing/analytics tag ids injected into every published page. |
 
 `analytics` is a flat map — include only the keys the site uses:

package/package.json

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