@uniweb/build 0.70.0 → 0.70.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.70.0",
+  "version": "0.70.1",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -57,11 +57,11 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/content-reader": "^1.2.7",
     "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/semantic-parser": "^1.4.1",
-    "@uniweb/schemas": "^0.9.0",
     "@uniweb/projections": "^0.7.9",
+    "@uniweb/content-reader": "^1.2.7",
+    "@uniweb/schemas": "^0.9.0",
+    "@uniweb/semantic-parser": "^1.4.1",
     "@uniweb/theming": "^0.1.16"
   },
   "optionalDependencies": {
@@ -74,8 +74,8 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.33.0",
-    "@uniweb/runtime": "^0.28.0"
+    "@uniweb/runtime": "^0.28.0",
+    "@uniweb/core": "^0.33.0"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/site/content-collector.js

@@ -749,8 +749,13 @@ function prettifySlug(slug) {
  *
  * A node with no sections of its own (a group/container node, a redirect stub)
  * has nothing to humanize from, so it shows the identifier the author actually
- * wrote — `v1` stays `v1`. A node with content falls back to its opening H1,
- * and only then to a prettified slug.
+ * wrote — `v1` stays `v1`. A node with content falls back to the opening H1 of
+ * its first section that publishes, and only then to a prettified slug.
+ *
+ * ⭐ "That publishes": a `hidden: true` section is a draft, so its heading never
+ * titles the page — in dev as in a published build, so the title does not change
+ * between them, and as a backend's publish does [2026-09-28]. A node whose sections
+ * are all hidden takes the prettified slug.
  *
  * The runtime has no fallback of its own: an empty title renders empty. The
  * fill belongs here, at the producer, because `title` also feeds `<title>`,
@@ -765,7 +770,8 @@ function prettifySlug(slug) {
 function resolveDisplayTitle(declaredTitle, segment, sections) {
   if (declaredTitle) return declaredTitle
   if (!sections?.length) return segment
-  return extractH1(sections[0]?.content) || prettifySlug(segment)
+  const first = sections.find((section) => section?.hidden !== true)
+  return extractH1(first?.content) || prettifySlug(segment)
 }
 
 // ⭐ The rule now lives in `utils/numeric-prefix.js` — `records/folder.yml` needs the
@@ -957,7 +963,9 @@ async function processFileAsPage(filePath, fileName, siteRoot, parentRoute) {
       version: null,
       versionMeta: null,
       versionScope: null,
-      hidden: false,
+      // The file IS the page, so its `hidden: true` drafts the page — left out of a published
+      // build, kept in dev — rather than leaving a page with no section (2026-09-28).
+      hidden: section.hidden === true,
       hideIn: [],
       layout: {},
       seo: {
@@ -2806,7 +2814,7 @@ export async function collectSiteContent(sitePath, options = {}) {
     // Dev keeps them so drafts stay previewable.
     pages: dropUnpublished ? dropUnpublishedPages(pages).map(withoutHiddenSections) : pages,
     // Layout area sets: { default: { header: page, footer: page, ... }, marketing: { ... } }
-    layouts: dropUnpublished ? mapLayoutAreas(layouts, withoutHiddenSections) : layouts,
+    layouts: dropUnpublished ? withoutHiddenAreas(layouts) : layouts,
     // ⭐ THE SAME REACHABILITY AXIS, for the 404 slot. `hidden: true` means DRAFT —
     // "excluded from the published site" (`docs/reference/page-configuration.md`);
     // `hideIn: ['*']` is the control for "routed but in no nav".
@@ -2836,16 +2844,23 @@ function withoutHiddenSections(page) {
   return { ...page, sections: dropHiddenSections(page.sections) }
 }
 
-// Apply `fn` to every area of every layout: `{ default: { header: page, … }, … }`.
-function mapLayoutAreas(layouts, fn) {
+// Every layout's areas without their hidden sections — and without an area whose sections
+// were all hidden: drafting every section of an area drafts the area, so a layout gets no area
+// there rather than an empty one (a backend's publish does the same).
+function withoutHiddenAreas(layouts) {
   if (!layouts || typeof layouts !== 'object') return layouts
   return Object.fromEntries(
-    Object.entries(layouts).map(([name, areas]) => [
-      name,
-      areas && typeof areas === 'object'
-        ? Object.fromEntries(Object.entries(areas).map(([area, page]) => [area, fn(page)]))
-        : areas,
-    ])
+    Object.entries(layouts).map(([name, areas]) => {
+      if (!areas || typeof areas !== 'object') return [name, areas]
+      const kept = {}
+      for (const [area, page] of Object.entries(areas)) {
+        const shown = withoutHiddenSections(page)
+        const hadSections = Array.isArray(page?.sections) && page.sections.length > 0
+        if (hadSections && shown.sections.length === 0) continue
+        kept[area] = shown
+      }
+      return [name, kept]
+    })
   )
 }
 

package/src/uwx/site.js

@@ -307,15 +307,16 @@ function mapSectionData(section) {
   // ⭐ A draft section — the store's own `hidden`, which an editor also writes [2026-09-28].
   if (section.hidden === true) data.hidden = true
   // No `preset` or `input`: nothing read either, and the collector drops them (2026-09-27).
-  // ⭐ `background` and `theme` stay IN `params` [Diego, 2026-09-28] — where the runtime reads
-  // them, and where a section stores them from now on. ⚠️ Also sent as the two fields they had
-  // until today, until every reader of a stored section reads `params`; a pull prefers a
-  // stored field meanwhile (`sectionRecordToFile`). uwx-format.md § A page section's fields.
+  // ⭐ `background` and `theme` ride IN `params` [Diego, 2026-09-28] — where the runtime reads
+  // them, and where a section stores them. ⛔ Not also as the `background` / `theme_override`
+  // fields, as build 0.69 sent them: every reader of a stored section reads `params` — a publish
+  // carries `params` whole, and the app reads a stored field first, then `params` — so nothing
+  // needs them, and a push that stops sending them lets a backend retire them without refusing
+  // it. A pull still prefers a stored field while one exists (`sectionRecordToFile`).
+  // uwx-format.md § A page section's fields, Order.
   if (Object.keys(params).length > 0) data.params = params
   data.content = section.content // leaf insets in it as written — no `insets` field since 2026-09-27
   setIf(data, 'fetch', section.fetch ?? undefined)
-  setIf(data, 'background', params.background)
-  setIf(data, 'theme_override', params.theme)
   return data
 }