uniweb 0.14.8 → 0.14.10

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": "0.14.8",
3
+ "version": "0.14.10",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -42,13 +42,13 @@
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.0.0",
44
44
  "@uniweb/core": "0.8.0",
45
- "@uniweb/runtime": "0.9.0",
46
- "@uniweb/kit": "0.10.8"
45
+ "@uniweb/runtime": "0.9.1",
46
+ "@uniweb/kit": "0.10.9"
47
47
  },
48
48
  "peerDependencies": {
49
- "@uniweb/build": "0.16.5",
50
49
  "@uniweb/content-reader": "1.2.2",
51
- "@uniweb/semantic-parser": "1.2.0"
50
+ "@uniweb/semantic-parser": "1.2.0",
51
+ "@uniweb/build": "0.16.6"
52
52
  },
53
53
  "peerDependenciesMeta": {
54
54
  "@uniweb/build": {
@@ -1511,6 +1511,8 @@ Layouts are full components with their own `params` in `meta.js`, not just struc
1511
1511
 
1512
1512
  **Layout `meta.js`** declares areas and optional scroll behavior: `{ areas: ['header', 'footer', 'left'], scroll: 'self' }`. Area names are arbitrary. `scroll` controls scroll restoration: unset = runtime manages `window` (default), `'self'` = the layout scrolls itself, or a CSS selector (`'main'`) = runtime manages that element.
1513
1513
 
1514
+ 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, but areas are equal to each other, so a layout whose chrome overlaps says which wins: `layers: { header: 2, left: 1 }`. 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.
1515
+
1514
1516
  **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"`.
1515
1517
 
1516
1518
  Layout sections are regular section types — they support the full content shape, including tagged data blocks, lists, links, and items. The only difference is they render on every page. Each content category takes a different role:
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-07-31T12:16:29.253Z",
3
+ "generatedAt": "2026-07-31T13:39:48.964Z",
4
4
  "packages": {
5
5
  "@uniweb/build": {
6
- "version": "0.16.5",
6
+ "version": "0.16.6",
7
7
  "path": "framework/build",
8
8
  "deps": [
9
9
  "@uniweb/content-reader",
@@ -45,7 +45,7 @@
45
45
  "deps": []
46
46
  },
47
47
  "@uniweb/kit": {
48
- "version": "0.10.8",
48
+ "version": "0.10.9",
49
49
  "path": "framework/kit",
50
50
  "deps": [
51
51
  "@uniweb/core",
@@ -59,7 +59,7 @@
59
59
  "deps": []
60
60
  },
61
61
  "@uniweb/press": {
62
- "version": "0.4.11",
62
+ "version": "0.4.12",
63
63
  "path": "framework/press",
64
64
  "deps": []
65
65
  },
@@ -72,7 +72,7 @@
72
72
  ]
73
73
  },
74
74
  "@uniweb/runtime": {
75
- "version": "0.9.0",
75
+ "version": "0.9.1",
76
76
  "path": "framework/runtime",
77
77
  "deps": [
78
78
  "@uniweb/core",