uniweb 0.9.6 → 0.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.9.6",
+  "version": "0.10.0",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,14 +41,14 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/runtime": "0.7.4",
-    "@uniweb/core": "0.6.1",
-    "@uniweb/kit": "0.8.2"
+    "@uniweb/core": "0.7.0",
+    "@uniweb/kit": "0.9.0",
+    "@uniweb/runtime": "0.8.0"
   },
   "peerDependencies": {
-    "@uniweb/build": "0.9.4",
     "@uniweb/content-reader": "1.1.4",
-    "@uniweb/semantic-parser": "1.1.9"
+    "@uniweb/semantic-parser": "1.1.9",
+    "@uniweb/build": "0.10.0"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -865,6 +865,38 @@ function MyComponent({ content, params, block }) {
 
 All non-reserved frontmatter fields become `params`. Reserved: `type`, `preset`, `input`, `data`, `id`, `background`, `theme`, `source`, `where`. Everything else flows to the component.
 
+### Data
+
+A component on a page with a `data:` or `fetch:` declaration automatically receives that data in `content.data.{schema}`. No opt-in required in `meta.js`. On a template page (`[slug]/`), the matched item is also delivered as `content.data.{singular}` (e.g. `content.data.article` when the parent declares `data: articles`).
+
+```jsx
+function Article({ content, block }) {
+  if (block.dataLoading) return <DataPlaceholder />
+  const article = content.data.article
+  if (!article) return <NotFound />
+  return <ArticleView article={article} />
+}
+```
+
+Components can ignore keys in `content.data` they don't need — the same way unused `params` are ignored. For declarative shape hints consumed by the editor and `prepare-props`, add `data: { entity: 'articles' }` to `meta.js`. For an explicit opt-out (rare), set `data: false`.
+
+**Authoring queries.** Fetch declarations (`fetch:` or the `data:` shorthand) accept query operators that describe which records you want, in what order, how many: `where:` (a where-object predicate), `sort:` (e.g. `date desc`), `limit:` (first N records). Whether the source evaluates them or the framework applies them as a runtime fallback is a transport detail controlled by the site's `fetcher.supports:` declaration.
+
+```yaml
+# pages/blog/page.yml
+fetch:
+  collection: articles
+  where: { published: true, tags: featured }
+  sort: date desc
+  limit: 3
+```
+
+**Lean lists with `deferred:`.** Collections with heavy fields (article bodies, large nested arrays) can declare `deferred: [body]` in `site.yml`. The cascade payload omits those fields; per-record full files are emitted at `/data/<name>/<slug>.json`. On dynamic-route pages the focused entity's full record is delivered automatically; elsewhere components fetch on demand via the `useEntityDetail` kit hook.
+
+**Component-side fetching.** When a component genuinely needs to fetch something on its own (a search box, a "load more" button, a popover that lazy-loads), use the kit hooks (`useFetched`, `useCacheEntry`, `useEntityDetail`). They share the framework's cache and dispatcher with declarative fetches; same-key requests dedupe automatically.
+
+See [Data Fetching](https://github.com/uniweb/docs/blob/main/reference/data-fetching.md) for the full model and [Predicates](https://github.com/uniweb/docs/blob/main/authoring/predicates.md) for the where-object format with examples.
+
 ### block properties
 
 | Property | Type | Description |

package/src/framework-index.json

@@ -1,9 +1,9 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-16T22:34:02.528Z",
+  "generatedAt": "2026-04-19T01:29:37.432Z",
   "packages": {
     "@uniweb/build": {
-      "version": "0.9.4",
+      "version": "0.10.0",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -24,7 +24,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.6.1",
+      "version": "0.7.0",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -42,7 +42,7 @@
       "deps": []
     },
     "@uniweb/kit": {
-      "version": "0.8.2",
+      "version": "0.9.0",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core"
@@ -54,12 +54,12 @@
       "deps": []
     },
     "@uniweb/press": {
-      "version": "0.2.4",
+      "version": "0.2.8",
       "path": "framework/press",
       "deps": []
     },
     "@uniweb/runtime": {
-      "version": "0.7.4",
+      "version": "0.8.0",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -82,7 +82,7 @@
       "deps": []
     },
     "@uniweb/templates": {
-      "version": "0.7.29",
+      "version": "0.7.31",
       "path": "framework/templates",
       "deps": []
     },
@@ -199,6 +199,20 @@
         "tables",
         "bibliography"
       ]
+    },
+    "academic-metrics": {
+      "name": "Academic Metrics (xlsx showcase)",
+      "description": "A docusite whose content is also a downloadable Excel workbook. Aggregates academic metrics (publications, funding, supervisions) across multiple members of a university unit. Rich web previews + flat tabular xlsx sheets from the same data. Ships with three 19th-century naturalists as sample members.",
+      "tags": [
+        "academic-metrics",
+        "docusite",
+        "press",
+        "xlsx",
+        "report",
+        "members",
+        "aggregate",
+        "academic"
+      ]
     }
   }
 }