uniweb 1.23.2 → 1.24.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "uniweb",
3
- "version": "1.23.2",
3
+ "version": "1.24.0",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -49,7 +49,7 @@
49
49
  "peerDependencies": {
50
50
  "@uniweb/semantic-parser": "~1.13.0",
51
51
  "@uniweb/content-reader": "~1.5.7",
52
- "@uniweb/build": "~1.12.2"
52
+ "@uniweb/build": "~1.13.0"
53
53
  },
54
54
  "peerDependenciesMeta": {
55
55
  "@uniweb/build": {
@@ -1616,10 +1616,12 @@ Semantic tokens come from `theme-tokens.css` (populated from `theme.yml`). Use `
1616
1616
 
1617
1617
  These compose with tokens — they adapt per context because they reference token variables — while adding nuance the token set doesn't provide. Use palette shades directly (`var(--primary-300)`, `bg-neutral-200`) for fine-grained control. **The priority: design quality > portability > configurability.** A beautiful foundation for one site is worth more than a generic one that looks flat.
1618
1618
 
1619
- Two lines a ported CSS reset will try to bring with it, both of which break things:
1619
+ Three lines a ported design will try to bring with it, each of which breaks something:
1620
1620
 
1621
1621
  > **Don't set `scroll-behavior: smooth` globally.** The runtime owns scrolling: it already smooth-scrolls anchor targets itself (`scrollIntoView({ behavior: 'smooth' })`), so the CSS adds nothing there — but it resets and restores scroll on route changes with the two-argument `scrollTo(x, y)`, which *inherits* the property. Route changes then animate their scroll-to-top, and back-button restoration (which scrolls, checks the position on the next frame, and retries) keeps interrupting its own animation. Scope it to a specific scrollable element if you need it; never to `html` or `body`.
1622
1622
 
1623
+ > **Paint a decorative glow with a gradient, not `filter: blur()`.** A `bg-primary-400 blur-[100px]` box is a soft glow, and a browser paints the filter again whenever it captures the page for a view transition. Safari does that on the main thread at device resolution, so on a phone a tap can freeze the page for seconds; a desktop in Chrome shows nothing. A radial mask looks the same and costs a fraction, and the box keeps its colour classes: `mask-image: radial-gradient(closest-side, #000, rgb(0 0 0 / 0.6) 40%, rgb(0 0 0 / 0.09) 80%, transparent)`.
1624
+
1623
1625
  > **Font smoothing is a per-scheme decision, not a reset.** `-webkit-font-smoothing: antialiased` (macOS only) forces grayscale rasterization, which thins strokes. On dark surfaces that usefully counteracts the bloom of light text on near-black; on light surfaces it costs contrast and makes body text spindly. Scope it — `.scheme-dark { -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; }` — rather than putting it on `html`.
1624
1626
 
1625
1627
  ### Composition: items, child sections, insets
@@ -1811,7 +1813,7 @@ Layouts are full components with their own `params` in `meta.js`, not just struc
1811
1813
 
1812
1814
  **Layout `meta.js`** declares areas and optional scroll behavior: `{ areas: ['header', 'footer', 'left'], scroll: 'self' }`. Area names are arbitrary. `areas` tells an editor what to offer; a page renders the areas its site's `layout/` folder fills. `scroll` controls scroll restoration: unset = runtime manages `window` (default), `'self'` = the layout scrolls itself, or a CSS selector (`'main'`) = runtime manages that element.
1813
1815
 
1814
- Two optional keys tune how areas behave across a navigation. `transitions` renames or opts regions out of per-area view transitions (`{ left: null }`, or `false` for the whole layout). `layers` sets which area paints on top — every area is stacked above the body by default, so a fixed header works without declaring anything, and a sticky area (one with a `sticky` section) above every area that does not stick, since the page scrolls under it. Otherwise areas are equal to each other, so a layout whose chrome overlaps says which wins: `layers: { header: 2, left: 1 }`, which also ranks a sticky area it names. Both take an object to override per region, or `false` to opt out. **A `z-index` inside an area cannot lift it past another area** — each area is its own stacking context — so reach for `layers` rather than a bigger number, and for `<Overlay>` when a modal needs to escape the area entirely.
1816
+ Two optional keys tune how areas behave across a navigation. `transitions` renames or opts regions out of per-area view transitions (`{ left: null }`, or `false` for the whole layout). The body has no name and crossfades with the page: Safari captures a named element whole, so naming it (`{ body: 'main' }`, for a body that morphs between layouts) freezes a phone on a long page. `layers` sets which area paints on top — every area is stacked above the body by default, so a fixed header works without declaring anything, and a sticky area (one with a `sticky` section) above every area that does not stick, since the page scrolls under it. Otherwise areas are equal to each other, so a layout whose chrome overlaps says which wins: `layers: { header: 2, left: 1 }`, which also ranks a sticky area it names. Both take an object to override per region, or `false` to opt out. **A `z-index` inside an area cannot lift it past another area** — each area is its own stacking context — so reach for `layers` rather than a bigger number, and for `<Overlay>` when a modal needs to escape the area entirely.
1815
1817
 
1816
1818
  **Layout content** lives in `site/layout/` — `header.md`, `footer.md` for the default layout, or a named subdirectory (`site/layout/marketing/`) for named layouts. Named subdirectories are self-contained — no inheritance. Cascade: `page.yml` → `folder.yml` → `site.yml` → foundation `defaultLayout` → `"default"`. The structure alone decides what an entry is: every folder directly under `layout/` is a named layout (its name matched regardless of case and of a trailing `Layout` — `site/layout/docs/` serves the foundation's `DocsLayout`), and an area with several sections is a folder inside a layout's folder — `site/layout/default/header/1-topbar.md` for the default layout. An area has no `page.yml`; its sections render in filename order.
1817
1819
 
@@ -413,9 +413,10 @@ function refusedReservedScope(scope, lead) {
413
413
  * foundation registered as `@jane/…` — releasable by Jane alone, and fixed only by
414
414
  * renaming it into a new foundation.
415
415
  *
416
- * When the workspace names no scope — none is chosen, or it is a unit without a handle —
417
- * the scope is derived from your orgs as before (`deriveScope`): your personal scope when
418
- * you belong to none, else a pick at a terminal, your personal scope without one.
416
+ * When the workspace names no scope — none is chosen, it is a unit without a handle, or a
417
+ * unit below an organization you are not a member of — the scope is derived from your orgs
418
+ * (`deriveScope`): your personal scope when you belong to none, else a pick at a terminal,
419
+ * and refused without one.
419
420
  */
420
421
  async function deriveScopeFromLogin(client, args) {
421
422
  const token = await client.token()
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-10-30T02:08:43.453Z",
3
+ "generatedAt": "2026-10-30T13:48:01.820Z",
4
4
  "packages": {
5
5
  "@uniweb/api": {
6
6
  "version": "1.6.7"
7
7
  },
8
8
  "@uniweb/build": {
9
- "version": "1.12.2"
9
+ "version": "1.13.0"
10
10
  },
11
11
  "@uniweb/content-reader": {
12
12
  "version": "1.5.7"
@@ -24,7 +24,7 @@
24
24
  "version": "1.0.7"
25
25
  },
26
26
  "@uniweb/kit": {
27
- "version": "1.6.8"
27
+ "version": "1.6.9"
28
28
  },
29
29
  "@uniweb/loom": {
30
30
  "version": "1.1.2"
@@ -36,7 +36,7 @@
36
36
  "version": "1.2.8"
37
37
  },
38
38
  "@uniweb/runtime": {
39
- "version": "1.2.14"
39
+ "version": "1.3.0"
40
40
  },
41
41
  "@uniweb/scene": {
42
42
  "version": "1.0.1"
@@ -54,13 +54,13 @@
54
54
  "version": "1.1.1"
55
55
  },
56
56
  "@uniweb/templates": {
57
- "version": "1.1.6"
57
+ "version": "1.1.7"
58
58
  },
59
59
  "@uniweb/theming": {
60
60
  "version": "1.2.1"
61
61
  },
62
62
  "@uniweb/unipress": {
63
- "version": "1.1.18"
63
+ "version": "1.1.19"
64
64
  }
65
65
  },
66
66
  "templates": {
@@ -201,7 +201,8 @@ export async function createOrg({ apiBase, token, handle }) {
201
201
  * ⚠️ The FALLBACK since 2026-10-06: a bare name first takes the workspace the command
202
202
  * works in (`register.js::deriveScopeFromLogin`, `workspace.js::scopeOfWorkspace`). This
203
203
  * answers only when no workspace is chosen — you belong to orgs and named none — or the
204
- * one chosen is a unit without a handle.
204
+ * one chosen names no scope: a unit without a handle, or a unit below an organization you
205
+ * are not a member of.
205
206
  *
206
207
  * ⭐ A SCOPE IS A NAMESPACE (2026-09-23): your account's own, `@<handle>`, needs no org.
207
208
  *