@sleekcms/sync 2.12.0 → 2.14.0

package/README.md

@@ -326,6 +326,7 @@ Models describe the shape of your content. They're JSON-like files with unquoted
 |---|---|
 | `render(val)` | Render a block or entry through its template |
 | `marked(md)` | Convert markdown to HTML |
+| `remark(md, opts?)` | Convert markdown to HTML with syntax-highlighted code blocks, math (`$…$`, `$$…$$`) and Mermaid diagrams, adding only the CSS/JS a page needs. `opts.codeTheme` picks a highlight.js theme (default `github-dark`) |
 
 **Images**
 
@@ -406,7 +407,11 @@ Models describe the shape of your content. They're JSON-like files with unquoted
 </form>
 ```
 
-Any form with `data-sleekcms="<name>"` captures and stores submissions in the CMS dashboard automatically.
+Any form with `data-sleekcms="<name>"` captures and stores submissions in the CMS dashboard automatically. File uploads work out of the box too — add an `<input type="file">` and visitors can attach documents (PDF, Word, Excel, CSV, text) and images:
+
+```html
+<input name="resume" type="file" accept=".pdf">
+```
 
 ---
 

package/dist/AGENT.md

@@ -203,7 +203,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 `<%- marked(item.x) %>` |
+| `markdown` | String of **raw markdown** — convert with `<%- marked(item.x) %>`, or `<%- remark(item.x) %>` when it holds code blocks, math or diagrams |
 | `number` | Number |
 | `boolean` | `true` / `false` |
 | `emoji` | One emoji character string, e.g. `"😀"` (not free text) |
@@ -350,7 +350,7 @@ Frontmatter may be JSON (canonical — prefer it when generating), JSON5, or YAM
 | Tag | Purpose |
 |---|---|
 | `<%= expr %>` | Output, HTML-escaped (plain text) |
-| `<%- expr %>` | Output raw HTML (`render()`, `img()`, `marked()`, richtext) |
+| `<%- expr %>` | Output raw HTML (`render()`, `img()`, `marked()`, `remark()`, richtext) |
 | `<% code %>` | Run JS (loops, conditionals) |
 
 ### Context variables (every view)
@@ -404,6 +404,18 @@ 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 |
 | `marked(md)` | Markdown string → HTML string |
+| `remark(md, opts?)` | Markdown string → HTML string, plus highlighted code blocks, math and Mermaid diagrams (below) |
+
+Use `remark()` instead of `marked()` for docs, tutorials and technical posts. On top of `marked()` it renders fenced code blocks (```` ```js ````) with syntax highlighting, 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, a code theme, the Mermaid runtime), so never `link()`/`script()` those libraries yourself.
+
+- `opts.codeTheme` — a highlight.js theme name: default `github-dark`, or e.g. `github`, `atom-one-dark`, `base16/dracula`. `github-dark` suits the dark `pre` that `prose` draws; use a light theme only when the site gives `pre` a light background. 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.
+
+```ejs
+<div class="prose prose-lg max-w-none"><%- remark(item.body) %></div>
+<%- remark(item.body, { codeTheme: 'github' }) %>  <!-- light code theme -->
+```
 
 ### Helpers — images & maps
 
@@ -491,6 +503,12 @@ Any `<form>` with `data-sleekcms="<hardcoded name>"` works automatically — sub
 
 The `data-sleekcms` value groups submissions by form; each input's `name` is stored as-is. Add an `<input type="datetime-local">` and the form becomes a **booking form** — see §11.
 
+**File uploads** are supported out of the box — add an `<input type="file">` and visitors can attach documents (PDF, Word, Excel, CSV, text) and images (add `multiple` for several):
+
+```html
+<input name="resume" type="file" accept=".pdf,.doc,.docx">
+```
+
 ## 11. Bookings
 
 Use this whenever visitors should **book or schedule** something — an appointment, a call, a demo, a consultation, a class, or a reservation ("pick a time / reserve a slot"). It fits appointment-based businesses: salon, spa, barber, dental/medical clinic, therapist, tutor, photographer, consultant, repair shop, restaurant reservations. **Only add a booking form when the business genuinely takes appointments and the user asks for it (or it is clearly core to the business) — never add one speculatively to an arbitrary site.**
@@ -655,7 +673,7 @@ No config element → all defaults. One per site: a second one is ignored with a
 3. Blocks never have content files. Block values live inline in the page/entry JSON that declares them.
 4. `file` field values are plain file names ending in a supported extension (`"brochure.pdf"`) — the CMS attaches or placeholder-creates the file server-side; never write objects or URLs.
 5. Never invent `video_id`/`embed_url` objects — render videos with `embed()` only. Videos are set via refs: `content/videos.json` handles for shared videos, and `cms:<handle>` / provider refs in `video` fields (§7); values that read back as embed URLs or objects are user uploads — leave them untouched.
-6. `richtext` → `<%- item.x %>`. `markdown` → `<%- marked(item.x) %>`.
+6. `richtext` → `<%- item.x %>`. `markdown` → `<%- marked(item.x) %>`, or `<%- remark(item.x) %>` when it holds code, math or diagrams.
 7. CSS/JS via `link()`/`script()` only; `css/tailwind.css` is auto-injected — never `link()` it. When writing tailwind.css, `@import "tailwindcss";` must stay as its first statement — dropping it silently removes all Tailwind styling.
 8. Editable copy belongs in `content/`, not hard-coded in `.ejs`. Fixed micro-labels may stay in views.
 9. In page keys, `-` separates words and `_` means `/`. `_index` is the home page only; a section index page uses the plain section key.

package/package.json

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