uniweb 1.13.1 → 1.13.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.13.1",
+  "version": "1.13.3",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/content-writer": "~1.3.0",
+    "@uniweb/core": "~1.3.0",
+    "@uniweb/semantic-parser": "~1.12.2",
     "@uniweb/schemas": "~1.5.0",
-    "@uniweb/semantic-parser": "~1.12.0",
-    "@uniweb/core": "~1.3.0"
+    "@uniweb/content-writer": "~1.3.0"
   },
   "peerDependencies": {
-    "@uniweb/content-reader": "~1.5.2",
-    "@uniweb/semantic-parser": "~1.12.0",
-    "@uniweb/build": "~1.5.1"
+    "@uniweb/build": "~1.5.2",
+    "@uniweb/content-reader": "~1.5.4",
+    "@uniweb/semantic-parser": "~1.12.2"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -1098,7 +1098,7 @@ import { Section, Prose } from '@uniweb/kit'
 
 `Prose` renders from the parsed sequence — headings, paragraphs, images, snippets, lists — with prose typography. Tagged data blocks are **skipped**; access them via `content.data` for custom rendering. Pass `content` (needs `.sequence`), and `block` too if the content uses insets. Also works as a pure typography wrapper: `<Prose>{children}</Prose>`.
 
-`Article` is an older alternative rendering from `block.rawContent` (raw ProseMirror), including data blocks. Prefer `Prose` for new components.
+`Article` is `Prose` in a semantic `<article>` element — the same rendering, for content that is a self-contained document.
 
 ### The Kit, by use case
 
@@ -1111,13 +1111,13 @@ Names only — for signatures and props, read the package: it's on disk at `node
 **Header/layout:** `useScrolled(threshold)`, `useMobileMenu()`, `useAppearance()`
 **Overlays:** `Overlay` (modals, palettes, drawers, toasts — portals out of the layout, contains focus; read the note below before hand-rolling one)
 **Keyboard:** `useShortcut('mod+k', fn)`, `useShortcuts({…})`, `useShortcutLabel('mod+k')` — `mod` is Cmd on Apple platforms and Ctrl elsewhere, and the label renders per-platform so a hint never shows the wrong key
-**Long-form prose:** `<Prose>` and the container you put `<Render>` output in both use Tailwind Typography's `prose` classes. One line in the foundation's `styles.css` supplies them and points them at the site's theme:
+**Long-form prose:** `<Prose>` and the container you put `<Render>` output in both use kit's `prose` classes. One line in the foundation's `styles.css` supplies the rules, colored by the section's theme:
 
 ```css
-@import "@uniweb/kit/prose-tokens.css";   /* the plugin, wired to theme.yml */
+@import "@uniweb/kit/prose-tokens.css";   /* kit's prose layer, wired to theme.yml */
 ```
 
-Nothing to install — the import brings the plugin with it. **Skip the import and prose is completely unstyled** — lists lose their bullets and numbers, and text its typography — while the markup looks right. The foundation build warns about it, and `uniweb doctor` flags it. Use **one** `prose` container per subtree — the `--tw-prose-*` variables are inherited, so a nested one silently resets them and the outer container goes on looking correct. The section that renders the document is usually the better owner; a layout should supply column width and padding.
+Nothing to install. **Skip the import and prose is completely unstyled** — lists lose their bullets and numbers, and text its typography — while the markup looks right. The foundation build warns about it, and `uniweb doctor` flags it. `size` picks a step (`prose-sm` … `prose-2xl`) of the site's reading size, which `theme.yml` sets under `vars:` — `prose-size`, `prose-leading`, `prose-measure`, `prose-flow`, `prose-h1` … `prose-h4`; spread `proseVars` from `@uniweb/kit/prose-vars` into `main.js`'s `vars` to declare them. `<Prose>` and `<Article>` fill their box (`max-w-none`), so `prose-measure` reaches only a `prose` element written without it — set their width on the box around them. A utility class or an element variant (`prose-headings:tracking-tight`, `prose-a:no-underline`) overrides any rule; `prose-a:` leaves a content button its own look. There are no palette modifiers and no `prose-invert` — the colors are already the theme's, light and dark.
 
 **Documentation shells:** `useHeadings()` (the page's headings + the one being read, derived from content so it prerenders), `website.getBranchHierarchy({ route, for })` (the page tree for one branch). Kit ships no ready-made layout — a layout is your foundation's design; write it in `src/layouts/` and use these for the behaviour.
 **Layout helpers:** `useGridLayout(columns, { gap })`, `useAccordion({ multiple, defaultOpen })`
@@ -1860,7 +1860,7 @@ const page = website.activePage
 | `block.childBlocks` / `block.insets` | Child sections / inline `@Component` references |
 | `block.getInset(refId)` | Lookup an inset by refId |
 | `block.properties` | Raw frontmatter |
-| `block.rawContent` | ProseMirror document — passed internally by `<Article block={block} />` |
+| `block.rawContent` | The section's ProseMirror document, before parsing — what a content handler reads |
 | `block.themeName` | `"light"`, `"medium"`, `"dark"` |
 | `block.stableId` / `block.key` | Stable ID from filename or `id:` / unique key across pages — use as React key |
 | `block.path` | Page route this block belongs to |
@@ -2566,6 +2566,24 @@ await writer.remove(itemId)
   first; a retry would succeed by overwriting a change nobody looked at. Tell the
   person.
 
+### Translated fields
+
+A `localized` field holds `{ en: '…', fr: '…' }`, or one plain value that is every
+language, and a read answers it in the page's language. ⛔ **Never write that one value
+back as the whole field** — it becomes the value in every language. To edit one:
+
+```jsx
+const { entity } = useEntity({ schema: '@/profile', uuid, languages: 'all' })   // every language, as stored
+await writer.update(item.id, { ...item.data, bio: 'Bonjour' }, { language: 'fr' }) // one language, merged
+```
+
+- **`update` with `{ language }`** merges each translated field you name into the languages
+  the item holds, and keeps a translated field you leave out. On a site with more than one
+  language, an update without it that writes a plain value over a translated field read in
+  the page's language is refused.
+- **`languagesOf`, `inLanguage` and `withLanguage`** read and set one language of a value
+  yourself, its `@` metadata kept.
+
 ### ⛔ Permissions are the SERVER'S, and your UI is only a courtesy
 
 Gate your controls on what the viewer may do — a record's own `can_edit` from a

package/src/commands/doctor.js

@@ -190,6 +190,38 @@ export function rendersKitProse(dir) {
   )
 }
 
+/**
+ * Does a stylesheet load Tailwind Typography itself? A line commented out loads
+ * nothing. ⛔ Until 2026-10-19 one was read as loaded, so the first step of
+ * removing the plugin drew a warning to remove it.
+ */
+export function loadsTypographyPlugin(styles) {
+  const css = String(styles || '').replace(/\/\*[\s\S]*?\*\//g, '')
+  return /@plugin\s+["']@tailwindcss\/typography["']/.test(css)
+}
+
+/**
+ * Tailwind Typography's palette modifiers and `prose-invert`, wherever a
+ * foundation's source names one in a class list — `dark:prose-invert` included,
+ * and marked important either way (`!prose-invert`, `prose-invert!`). Comments
+ * are skipped, since a comment warning against one names it too. What it reads
+ * is the source's text, so the same word in a sentence a component renders is
+ * read as a class as well.
+ *
+ * @returns {{ file: string, modifiers: string[] }[]}
+ */
+export function inertProseModifiers(dir) {
+  const MODIFIER =
+    /(?:^|[\s"'`:!])(prose-(?:gray|slate|zinc|neutral|stone|invert|red|orange|amber|yellow|lime|green|emerald|teal|cyan|sky|blue|indigo|violet|purple|fuchsia|pink|rose))(?=$|[\s"'`!])/gm
+  const found = []
+  forEachSourceFile(dir, (text, file) => {
+    const code = text.replace(/\/\*[\s\S]*?\*\//g, '').replace(/(^|[^:])\/\/.*$/gm, '$1')
+    const modifiers = [...new Set([...code.matchAll(MODIFIER)].map((m) => m[1]))]
+    if (modifiers.length) found.push({ file, modifiers })
+  })
+  return found
+}
+
 function sourceMatches(dir, pattern) {
   let found = false
   forEachSourceFile(dir, (text) => {
@@ -1200,13 +1232,14 @@ export async function doctor(args = []) {
 
   // Prose without the tokens — a silent, total loss of styling.
   //
-  // `@uniweb/kit/prose-tokens.css` brings Tailwind Typography with it and then
-  // points it at the site's theme.yml. A foundation that writes `prose` (or
-  // renders <Prose>/<Article>, which emit it) and does NOT import that file
-  // gets the class and no rules behind it: correct markup, zero styling, and
-  // nothing reported anywhere. Measured 2026-07-30 on a foundation missing only
-  // the plugin — every paragraph `margin-top: 0px`, no warning from Vite,
-  // Tailwind or the browser.
+  // `@uniweb/kit/prose-tokens.css` is kit's prose layer, which answers to the
+  // site's theme.yml. A foundation that writes `prose` (or renders
+  // <Prose>/<Article>, which emit it) and does NOT import that file gets the
+  // class and no rules behind it: correct markup, zero styling, and nothing
+  // reported anywhere. Measured 2026-07-30 on a foundation missing only the
+  // rules — every paragraph `margin-top: 0px`, no warning from Vite, Tailwind or
+  // the browser. (Then the rules were Tailwind Typography's; kit's own since
+  // 2026-10-19.)
   //
   // kit closes this for anyone who imports the file; this closes it for anyone
   // who does not, which is the case kit cannot reach.
@@ -1237,13 +1270,63 @@ export async function doctor(args = []) {
     })
     warn(`[${id}] ${f.name} ${reason}, with no prose styling behind it`)
     log(
-      `    Tailwind Typography supplies the rules and it is not loaded, so the ` +
+      `    kit's prose layer supplies the rules and it is not imported, so the ` +
       `markup is correct and completely unstyled — silently.`
     )
     log(`    Add to ${f.folderName}/styles.css:`)
     log(`      ${colors.dim}@import "@uniweb/kit/prose-tokens.css";${colors.reset}`)
   }
 
+  // A modifier kit's prose layer does not have — `prose-slate`, `prose-invert`
+  // and the rest of Tailwind Typography's palettes. Since 2026-10-19 the layer
+  // takes every color from the section's theme tokens, so a class list still
+  // naming one styles nothing and says a design the page does not have.
+  // Only where the foundation imports kit's layer and does not load the plugin
+  // itself — with its own `@plugin`, the modifier still means what it says.
+  for (const f of foundations) {
+    const stylesPath = join(f.path, 'styles.css')
+    if (!existsSync(stylesPath)) continue
+    const styles = readFileSync(stylesPath, 'utf8')
+    if (!styles.includes('@uniweb/kit/prose-tokens.css')) continue
+    if (loadsTypographyPlugin(styles)) {
+      // Both: the plugin's rules sit in a layer above kit's and win, so prose is
+      // the plugin's again — its own greys, and none of the --prose-* variables.
+      const id = 'prose-plugin-alongside'
+      issues.push({
+        id,
+        type: 'warning',
+        foundation: f.name,
+        message: `${f.name} loads Tailwind Typography as well as kit's prose layer`
+      })
+      warn(`[${id}] ${f.name} loads Tailwind Typography as well as kit's prose layer`)
+      log(
+        `    The plugin's rules sit above kit's and win: prose takes the plugin's greys, not the ` +
+        `theme's colors, and the --prose-* variables reach nothing.`
+      )
+      log(`    Remove the @plugin line from ${f.folderName}/styles.css to use kit's layer alone.`)
+      continue
+    }
+
+    const found = inertProseModifiers(f.path)
+    if (found.length === 0) continue
+
+    const id = 'prose-modifier-inert'
+    const names = [...new Set(found.flatMap((x) => x.modifiers))]
+    issues.push({
+      id,
+      type: 'warning',
+      foundation: f.name,
+      message: `${f.name} names ${names.join(', ')}, which kit's prose layer does not have`
+    })
+    warn(`[${id}] ${f.name} names ${names.join(', ')} — they no longer do anything`)
+    for (const { file, modifiers } of found.slice(0, 6)) log(`    ${file}: ${modifiers.join(', ')}`)
+    log(
+      `    Prose takes its colors from the section's theme tokens, so it already follows ` +
+      `theme.yml and the visitor's scheme. Remove these; to change what prose looks like, ` +
+      `set the theme's colors, or the --prose-* variables.`
+    )
+  }
+
   // ⛔ SAY WHEN A CHECK DID NOT RUN. Every foundation check below reads the
   // BUILT `dist/meta/schema.json` — what a consumer actually receives — and
   // returns silently when there is none. In a workspace with a site, "Foundation

package/src/framework-index.json

@@ -1,15 +1,15 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-19T02:42:59.650Z",
+  "generatedAt": "2026-10-19T18:20:17.536Z",
   "packages": {
     "@uniweb/api": {
-      "version": "1.5.2"
+      "version": "1.6.0"
     },
     "@uniweb/build": {
-      "version": "1.5.1"
+      "version": "1.5.2"
     },
     "@uniweb/content-reader": {
-      "version": "1.5.2"
+      "version": "1.5.4"
     },
     "@uniweb/content-writer": {
       "version": "1.3.0"
@@ -24,7 +24,7 @@
       "version": "1.0.4"
     },
     "@uniweb/kit": {
-      "version": "1.4.0"
+      "version": "1.5.1"
     },
     "@uniweb/loom": {
       "version": "1.1.0"
@@ -36,7 +36,7 @@
       "version": "1.1.4"
     },
     "@uniweb/runtime": {
-      "version": "1.1.8"
+      "version": "1.1.10"
     },
     "@uniweb/scene": {
       "version": "1.0.1"
@@ -48,13 +48,13 @@
       "version": "1.1.0"
     },
     "@uniweb/semantic-parser": {
-      "version": "1.12.0"
+      "version": "1.12.2"
     },
     "@uniweb/snapshot": {
       "version": "1.1.0"
     },
     "@uniweb/templates": {
-      "version": "1.1.1"
+      "version": "1.1.3"
     },
     "@uniweb/theming": {
       "version": "1.2.0"