uniweb 1.22.0 → 1.22.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.22.0",
+  "version": "1.22.2",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.3.2",
     "prompts": "^2.4.2",
     "tar": "^7.5.21",
-    "@uniweb/schemas": "~1.6.5",
-    "@uniweb/content-writer": "~1.3.1",
     "@uniweb/semantic-parser": "~1.13.0",
-    "@uniweb/core": "~1.4.12"
+    "@uniweb/core": "~1.4.12",
+    "@uniweb/content-writer": "~1.3.1",
+    "@uniweb/schemas": "~1.6.6"
   },
   "peerDependencies": {
     "@uniweb/semantic-parser": "~1.13.0",
-    "@uniweb/content-reader": "~1.5.7",
-    "@uniweb/build": "~1.11.0"
+    "@uniweb/build": "~1.11.2",
+    "@uniweb/content-reader": "~1.5.7"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -546,7 +546,7 @@ Optional attributes: `{size=20}`, `{color=red}`. Custom SVGs: `![Logo](./logo.sv
 
 Sizing and loading ride on the image: `{width=800 height=600 loading=lazy fit=cover position=center}`, and its credit as `{author="Jane Doe"}`. A video adds `{poster=./thumb.jpg autoplay muted loop controls}`; a `{role=pdf}` document adds `{preview=./cover.jpg author=… description=…}` and arrives in `content.documents` — `{ url, name, mime, size?, alt, caption, … }` — declare it in `content:` as `documents`. Name a video's poster: a static build makes one from the video only when none is named and ffmpeg is installed, and `uniweb publish` sends only the poster you name.
 
-**Where media lives.** `./x` names a file beside the page, `/x` a file in `public/`, and both reach a static build and a site published with Uniweb. Keep a page's media beside it, and keep in `public/` what needs a fixed address: the favicon, fonts, a file other sites link to. `uniweb push` uploads a file beside a page wherever the page is, in a folder `paths:` mounts too; a file outside the site and the folders it mounts is not uploaded, so put that in `public/`. A site has no `assets/` folder for media: a build stops on a `/x` only `assets/` holds.
+**Where media lives.** `./x` names a file beside the page, `/x` a file in `public/`, and both reach a static build and a site published with Uniweb. Keep a page's media beside it, and keep in `public/` what needs a fixed address: the favicon, fonts, a file other sites link to. A static build copies `public/` whole and adds its own copy of each file a page names there, so a video only a page shows is in `dist/` twice from `public/` and once from beside the page. `uniweb push` uploads a file beside a page wherever the page is, in a folder `paths:` mounts too; a file outside the site and the folders it mounts is not uploaded, so put that in `public/`. A site has no `assets/` folder for media: a build stops on a `/x` only `assets/` holds.
 
 **Placement — where a block sits in a section rendered in order.** `{placement=left}` (or `right`, `wide`, `full`) on an image or a video; a table takes it on its **caption line**, the paragraph after the table, after a blank line — `: Plans and prices {placement=wide #tbl-plans}`, which also gives the table a caption and a cross-reference id. It is the author's intent, not a size: kit's `<Render>`, `<Prose>` and `<Article>` lay all four out (`data-placement`, styled by `prose-tokens.css`), and any other component ignores it. A section type says which it honours in `meta.js` — `sequence: { label, placement: true }` — and the build warns when a file asks for one its type does not offer.
 
@@ -952,7 +952,7 @@ The body — the value of the schema's content field, `body.content`.
 
 A path under a folder is relative to `records/`, naming one file or matching many. A record's entry can instead be `{ path, tags, label }` — what the folder says about the record: a component receives them beside it as `$tags` (in the order written) and `$label`, and a query reads them like any key (`where: { $tags: featured }`); such an entry may sit at the top level, where a bare path is refused. A `label` — a record entry's or a folder's — is one text in the site's language, or one per language (`label: { en: Launch video, fr: Vidéo de lancement }`); `$label` is the page's language, else its base language, else the site's. A folder takes `tags:` too. A query reads one folder with `scope: archive` — the folder and everything inside it. A record sits in one folder; if you want a computed subset, that is a query, not a second placement. Structure is for querying, not for navigation — and `folder.yml` never lists a record at the top level (the build refuses it: every file in `records/` is a record already).
 
-⚠️ **With a backend, `records/` is what `uniweb push` sends** — every record in it. A site with no `records/` at all leaves the backend's records alone; an *empty* `records/` removes them, and the CLI asks before it does. Records pushed to a backend are served once the site is published.
+⚠️ **With a backend, `records/` is what `uniweb push` sends** — every record in it. A site with no `records/` at all leaves the backend's records alone; an *empty* `records/` removes them, and the CLI asks before it does. Records pushed to a backend are served once the site is published: a record with a data schema reaches the published pages only when `services:` asks for `records: true`, and one with none travels as the published site's files.
 
 **`queries.yml` — how content is reached.** A bare map of name → query. A query names a schema and the site's records of that schema are its rows:
 
@@ -2948,8 +2948,9 @@ YAML, not switches — write `true` or `false`. On a site you push or publish it
 its service, `false` asks it to turn its service off, and an address asks it to leave its own off so
 yours answers. **On a site your host publishes, a service is off unless `services:` asks for it** —
 list the ones the site uses (the templates list theirs). `records: true` asks for your records to be
-delivered live to the published pages: a query whose records have a data schema shows nothing there
-without it, and `publish` says so; a static build reads records from files and ignores it. An entry
+delivered live to the published pages. Turn it on before the first publish of a page that shows
+records with a data schema: without it those records never reach the published page, and `publish`
+warns. A static build reads records from files and ignores it. An entry
 says everything about its service: a setting you remove from it is removed on the next push, and
 removing the entry switches the service off. `uniweb push` and `uniweb publish` send each service
 `site.yml` lists; a service the site has that this copy has never seen (turned on in the app since
@@ -3076,10 +3077,12 @@ These are **body only — no frontmatter**; params and config still come from th
 
 **A tagged data block translates by the shape its key declares** in the component's `meta.js` `data:` — a data schema or an inline field map: its text fields, never an enum, a URL or a `translatable: false` field. A key declared `{}` leaves its blocks to a heuristic that offers any string whose field name and value don't look structural, so a `style: display-black` naming one of your component's looks gets translated too. Declare the shape of every block a translator will see — `{ name: 'string', style: { type: 'string', enum: [...] } }`.
 
-**An image translates by its alt text.** Words alone give it its alt text in that language and keep its file. A translation that is an image also names the file that language shows: `"2d093636": "![La superposition](/docs-media/fr/overview.png)"`. Name it with a `/` path, a file in `public/`. A caption or a video's `poster` can be given the same way. An image with no alt text has nothing to translate, so give every image one.
+**An image translates by its alt text.** Words alone give it its alt text in that language and keep its file. A translation that is an image also names the file that language shows: `"2d093636": "![La superposition](/docs-media/fr/overview.png)"`. Name it with a `/` path, a file in `public/`, and a build processes it as it does the page's own images; a `./` path has no page's folder to start from, and the build reports it. A caption or a video's `poster` can be given the same way. An image with no alt text has nothing to translate, so give every image one.
 
 **Records translate in the same `extract` run**, into their own manifest at `locales/records/manifest.json` — keyed by the RECORD, so a record translated once is found by every query that returns it. A record whose query has a data schema translates exactly the fields the schema says are text — never an enum, a URL, a date, a number, a file, a reference or a `translatable: false` field — which are the fields a push carries in each language; mark a string that is a code or a key `translatable: false` and no translator is asked for it. An excerpt the build derives is re-derived from each language's body.
 
+**A data schema's own labels are not in `locales/`.** The schema's `label`, `plural`, `description` and its sections' and fields' labels are written once, in its `source_locale`; their other languages go in the schema's `i18n`, keyed by path: `i18n: { fr: { model.label: Séance, section.brief.field.title.label: Titre } }`. A section is named by its full path (`contributions/publications`), and a `fields:` schema's one section is `brief`. See `development/data-schemas.md`.
+
 **Component side.** Nothing to do: `content.title` arrives in the active language. The one thing a foundation builds is a switcher.
 
 ```jsx

package/src/commands/build.js

@@ -69,10 +69,6 @@ import {
   isExtensionPackage,
   detectFoundationType
 } from '@uniweb/build'
-import {
-  resolveDefaultLocale,
-  normalizeLanguageList
-} from '@uniweb/core/locale-config'
 import { readSiteConfig } from '@uniweb/build/site'
 import { workspacePackages } from '../utils/workspace-packages.js'
 
@@ -424,34 +420,25 @@ async function loadI18nConfig(projectDir, siteConfig = null) {
   const localesDir = config.i18n?.localesDir || 'locales'
   const localesPath = join(projectDir, localesDir)
 
-  // Resolve locales (undefined/'*' → all available, array → specific)
-  const { resolveLocales } = await import('@uniweb/build/i18n')
-  let locales = await resolveLocales(config.languages, localesPath)
-
-  // Publish filter: build outputs are visitor artifacts. With an explicit
-  // `publishLanguages:`, only listed locales get dist/{locale}/ content,
-  // per-locale HTML, hreflang, and translated collections. Draft locales
-  // stay previewable in dev, which doesn't run this path. Intersecting the
-  // DISK-resolved list here also covers wildcard (`languages: '*'`) sites.
-  if (config.publishLanguages != null) {
-    const publishSet = new Set(normalizeLanguageList(config.publishLanguages))
-    const dropped = locales.filter((l) => !publishSet.has(l))
-    locales = locales.filter((l) => publishSet.has(l))
-    if (dropped.length > 0) {
-      info(
-        `Skipping non-publishable locale(s): ${dropped.join(', ')} (not in publishLanguages)`
-      )
-    }
+  // The site's locales (undefined/'*' → all available, array → specific), with
+  // two filters, by the rule the bundle uses to decide whose files to process
+  // (`localesToBuild`):
+  // - Publish: build outputs are visitor artifacts. With an explicit
+  //   `publishLanguages:`, only listed locales get dist/{locale}/ content,
+  //   per-locale HTML, hreflang, and translated collections. Draft locales
+  //   stay previewable in dev, which doesn't run this path. Intersecting the
+  //   DISK-resolved list also covers wildcard (`languages: '*'`) sites.
+  // - ⛔ The default locale is the root tree, not `dist/<default>/`. An explicit
+  //   `languages: [en, fr]` resolves verbatim — default included — so the DECLARED
+  //   form (the one the contract tells authors to use) minted a duplicate copy of
+  //   every page, while the wildcard form did not. Dropping it keeps content,
+  //   per-locale HTML and translated records agreeing on one set.
+  const { localesToBuild } = await import('@uniweb/build/i18n')
+  const { locales, skipped, defaultLocale } = localesToBuild(config, localesPath)
+  if (skipped.length > 0) {
+    info(`Skipping non-publishable locale(s): ${skipped.join(', ')} (not in publishLanguages)`)
   }
 
-  // ⛔ The default locale is the root tree, not `dist/<default>/`. An explicit
-  // `languages: [en, fr]` resolves verbatim — default included — so the DECLARED
-  // form (the one the contract tells authors to use) minted a duplicate copy of
-  // every page, while the wildcard form did not. Dropping it here keeps content,
-  // per-locale HTML and translated records agreeing on one set.
-  const defaultLocale = resolveDefaultLocale(config)
-  locales = locales.filter((l) => l !== defaultLocale)
-
   if (locales.length === 0) return null
 
   return {

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-29T01:09:12.877Z",
+  "generatedAt": "2026-10-29T14:12:43.968Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.6.5"
     },
     "@uniweb/build": {
-      "version": "1.11.0"
+      "version": "1.11.2"
     },
     "@uniweb/content-reader": {
       "version": "1.5.7"
@@ -42,7 +42,7 @@
       "version": "1.0.1"
     },
     "@uniweb/schemas": {
-      "version": "1.6.5"
+      "version": "1.6.6"
     },
     "@uniweb/scholar": {
       "version": "1.1.0"