@sleekcms/sync 4.0.0 → 4.1.0

package/README.md

@@ -414,7 +414,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, 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 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
 {
@@ -422,6 +422,7 @@ Site-wide decisions made once — the default page title, whether Tailwind is co
   tw_enabled: true,         // compile src/public/css/tailwind.css and inject it into every page
   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
   analytics: {              // tag ids injected into every page; include only the ones you use
     ga4: "G-XXXXXXXXXX",
   },

package/dist/AGENTS.md

@@ -118,6 +118,7 @@ setup.json                      Site setup (JSON, comments allowed): default pag
 | `tw_enabled` | boolean | `true` compiles `css/tailwind.css` and injects it into every page — required for any site styled with Tailwind utilities. |
 | `sitemap_enabled` | boolean | `true` publishes `sitemap.xml` + `robots.txt` on every build. Turn it on for public sites and SEO work. |
 | `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. |
 | `analytics` | object | Marketing/analytics tag ids injected into every published page. |
 
 `analytics` is a flat map — include only the keys the site uses:
@@ -203,7 +204,7 @@ Like JSON but with **no quotes**; each value is a field type name:
 |---|---|
 | `text`, `paragraph`, `code`, `color`, `link` | String |
 | `richtext` | String of **HTML** — output with `<%- %>` |
-| `markdown` | String of **raw markdown** — convert with `<%- remark(item.x) %>` (see Helpers — rendering) |
+| `markdown` | String of **raw markdown** — convert with `<%- remark(item.x) %>`, which renders GFM (tables, task lists, footnotes), syntax-highlighted code fences, math (`$…$`, `$$…$$`) and ```` ```mermaid ```` diagrams as SVG (see Helpers — rendering) |
 | `number` | Number |
 | `boolean` | `true` / `false` |
 | `emoji` | One emoji character string, e.g. `"😀"` (not free text) |
@@ -405,11 +406,11 @@ There is exactly **one** layout: `layouts/common.ejs`. It wraps every page autom
 | `render(val, separator?)` | Render a block, entry, or array of them through its `blocks/<key>.ejs` / `entries/<key>.ejs` view. An `entries/<key>.ejs` view is only needed if you call `render()` on that entry — otherwise just use its data directly |
 | `remark(md, opts?)` | Markdown string → HTML string, with build-time highlighted code blocks, math and Mermaid diagrams (below) |
 
-Render every `markdown` field with `remark()`, whatever it holds today — editors add code, math and diagrams later; plain prose comes out as ordinary HTML with nothing injected. On top of standard markdown (including GFM tables, task lists and footnotes) it renders fenced code blocks (```` ```js ````) with syntax highlighting at build time, math written as `$e^{i\pi} + 1 = 0$` inline, `$$ … $$` on its own lines or a ```` ```math ```` fence (KaTeX), and ```` ```mermaid ```` fences as diagrams drawn in the visitor's browser. It injects only the CSS/JS the rendered markdown needs (KaTeX CSS, the code theme, the Mermaid runtime). **Never rebuild any of it yourself:** no highlight.js, Prism, KaTeX or Mermaid via `link()`/`script()`, and no `public/js` that highlights `pre code`, converts `language-mermaid` blocks or renders math.
+Render every `markdown` field with `remark()`, whatever it holds today — editors add code, math and diagrams later; plain prose comes out as ordinary HTML with nothing injected. On top of standard markdown (including GFM tables, task lists and footnotes) it renders fenced code blocks (```` ```js ````) with syntax highlighting at build time, math written as `$e^{i\pi} + 1 = 0$` inline, `$$ … $$` on its own lines or a ```` ```math ```` fence (KaTeX), and ```` ```mermaid ```` fences as diagrams, drawn as SVG at build time. It injects only the CSS/JS the rendered markdown needs (KaTeX CSS, the code theme, the diagram styles). **Never rebuild any of it yourself:** no highlight.js, Prism, KaTeX or Mermaid via `link()`/`script()`, and no `public/js` that highlights `pre code`, converts `language-mermaid` blocks or renders math.
 
 - `opts.codeTheme` — a highlight.js theme name: default `github-dark`, or e.g. `github`, `atom-one-dark`, `base16/dracula`. The theme sets the token colors and the code box's background together, so pick code colors with `codeTheme`, never CSS: don't restyle `.hljs` / `pre code` colors or backgrounds, and don't clear `pre`'s background (`prose-pre:bg-transparent`) — a dark theme's light text on a light page all but disappears. `github-dark` suits the dark `pre` that `prose` draws; use `github` only when the design wants light code blocks. One theme per page.
 - A single-`$` pair is math only when it hugs its content (`$x^2$`), so prices like "$5 to $10" stay text. Escape a dollar that must stay literal as `\$`.
-- Mermaid uses its light default theme. On a dark design, start each diagram with frontmatter: `---`, `config:`, `  theme: dark`, `---` on their own lines above the diagram.
+- Diagrams use Mermaid syntax (flowchart, sequence, class, state, ER, Gantt, pie and the other built-in types) and match the page's light or dark design on their own: don't style or theme them (no `theme` config, no CSS). Labels are plain text — no HTML.
 
 ```ejs
 <div class="prose prose-lg max-w-none"><%- remark(item.body) %></div>

package/package.json

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