uniweb 0.48.4 → 0.48.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.48.4",
+  "version": "0.48.5",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/core": "^0.24.3",
-    "@uniweb/kit": "^0.18.1",
-    "@uniweb/runtime": "^0.19.4",
+    "@uniweb/runtime": "^0.19.5",
+    "@uniweb/core": "^0.24.4",
+    "@uniweb/kit": "^0.18.2",
     "@uniweb/semantic-parser": "^1.4.0"
   },
   "peerDependencies": {
-    "@uniweb/content-reader": "^1.2.4",
     "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/build": "^0.44.3"
+    "@uniweb/content-reader": "^1.2.4",
+    "@uniweb/build": "^0.44.4"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -86,7 +86,7 @@ Documentation paths in this guide are given bare — `development/creating-compo
 | Theming and styling | `authoring/theming.md` |
 | Authoring collections | `authoring/collections.md` |
 | Where-object predicate format | `authoring/predicates.md` |
-| Connecting a backend / custom transports | `development/connecting-a-backend.md` |
+| Data sources / custom transports | `development/data-sources.md` |
 | Building components | `development/creating-components.md` |
 | Schemas in practice | `development/schemas-in-practice.md` |
 | Workspace layouts and their wiring | `development/project-structures.md` |
@@ -1843,7 +1843,7 @@ fetcher:
 
 **Failures are visible, not empty:** a fetch that failed leaves its key ABSENT from `content.data` and names the message on `block.dataError[key]`; it is never delivered as `[]`, which means "no records". The page still renders — a section reads `dataError` to tell the two apart.
 
-When a plain `url:` is enough and when a transport is the answer: `development/connecting-a-backend.md`.
+When a plain `url:` is enough and when a transport is the answer: `development/data-sources.md`.
 
 Full model: `reference/data-fetching.md`. Where-object format with examples: `authoring/predicates.md`.
 
@@ -1895,16 +1895,18 @@ section type, same arrangement as `fetcher:` and `search:`.
 
 A form gets its destination from the first of these that applies:
 
-1. **`submit:` in `site.yml`** — an endpoint you name yourself.
-2. **One the host supplies** — `services.submit` in the served payload. A site
-   published to Uniweb Cloud gets submission handling from the platform, so it
-   normally needs **no `submit:` at all**.
+1. **One the host supplies** — `services.submit` in the served payload. Where the
+   host handles submissions, that is the destination and nothing in `site.yml`
+   overrides it — so a site published to Uniweb Cloud normally needs **no
+   `submit:` at all**.
+2. **`submit:` in `site.yml`** — an endpoint you name yourself, for a host that
+   does not handle submissions, or a static site.
 3. **Neither** — there is no destination, and the form says so instead of
    guessing at one.
 
 That is the general arrangement, not a forms-only one. A host declares
 everything it offers under `services`, keyed by name, and every service resolves
-by the same rule — your declaration, then the host's, then neither.
+by the same rule — the host's offer, then your declaration, then neither.
 
 ⭐ **Before you render UI for a service, ask whether the site has it** — one predicate per service,
 no arguments: `isSearchEnabled()`, `isSubmitEnabled()`, `isApiEnabled()`, `isAssistantEnabled()`,
@@ -2097,7 +2099,7 @@ tracking:
 ```
 
 A host may also supply one under `services.tracking`, and the usual precedence
-applies: yours wins, then the host's, then neither.
+applies: the host's, then yours, then neither.
 
 ⚠️ **The endpoint has to accept the framework's own format** — a batched
 `{ "events": [ … ] }` POST, documented in `reference/site-configuration.md`. It
@@ -2166,17 +2168,18 @@ tracking:
 ⭐ **`emit` needs no endpoint of its own.** Where a host provides one, the site
 declares only what it wants sent and the address comes from the host. The two
 are read key by key, so naming `emit` alone overrides nothing else the host
-declared. And declaring your own `endpoint:` always wins, so a site pointing at
-its own collector keeps working on any host, including none.
+declared. An `endpoint:` of your own is used wherever the host supplies no
+collector — on a host without one, and on none — and where the host supplies
+one, the host's is used.
 
-`minimal` is `page_view` alone. `standard` is the default when you supply your
-own `endpoint:`. `all` is a standing yes, so an event added in a later framework
+`minimal` is `page_view` alone. `standard` is the default when the collector is
+your own. `all` is a standing yes, so an event added in a later framework
 release is included without you changing anything — which is exactly why
 `standard` exists as well: it is a curated set that a release cannot grow behind
 your back.
 
 ⭐ **Saying nothing means two different things, and which one depends on who
-supplies the address.** A site with its own `endpoint:` gets `standard`. A site
+supplies the address.** A site sending to its own `endpoint:` gets `standard`. A site
 on a **host-supplied** collector gets **whatever that host declares it
 collects** — it has no address of its own, so the arrangement is that the host
 does analytics for it, and the set grows when the host starts collecting
@@ -2324,10 +2327,10 @@ For cases the factory doesn't cover, write handlers directly using `Loom`, `inst
 ## Part 4b — When the site is also an app
 
 Everything above is a site: content the author writes, built into pages. Some sites
-also have **their own backend** — accounts, per-visitor data, records their members
-create and edit. That is `@uniweb/api`.
+also have **an `api` service** — accounts, per-visitor data, records their members
+create and edit. `@uniweb/api` is its client.
 
-⛔ **Only reach for this when the site actually has one.** A site with no backend is
+⛔ **Only reach for this when the site actually has one.** A site without one is
 the normal case, and a foundation that assumes one breaks on every other site it is
 used with.
 
@@ -2344,7 +2347,7 @@ import { useSession, SignedIn, SignedOut } from '@uniweb/api'
 if (!isApiEnabled()) return <StaticVersion />   // synchronous — nothing to await
 ```
 
-⛔ **When there is no backend, draw nothing** — not a disabled control, and not an
+⛔ **When the site has no `api` service, draw nothing** — not a disabled control, and not an
 explanation. Same rule as `services` in Part 4: which capabilities a site's operator
 set up is none of a visitor's business, and "sign-in unavailable" reads as breakage
 when it is simply a feature this site does not have. Render the version of your
@@ -2357,8 +2360,8 @@ const { status, records } = useRecords({ schema: '@/session' })
 ```
 
 ⭐ **`absent` and an empty `ready` are different answers, and confusing them is the
-mistake to avoid.** `absent` = there is no live source (no backend, or nobody signed
-in) → render the site's authored content. `ready` with `records: []` = the backend
+mistake to avoid.** `absent` = there is no live source (no `api` service, or nobody signed
+in) → render the site's authored content. `ready` with `records: []` = the service
 answered and there is nothing there → render your empty state. Showing "nothing yet"
 for the first tells a visitor their content is gone when it was never requested.
 

package/src/framework-index.json

@@ -1,16 +1,16 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-09-10T14:59:00.380Z",
+  "generatedAt": "2026-09-10T16:24:13.926Z",
   "packages": {
     "@uniweb/api": {
-      "version": "0.3.0",
+      "version": "0.3.1",
       "path": "framework/api",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/build": {
-      "version": "0.44.3",
+      "version": "0.44.4",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -34,7 +34,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.24.3",
+      "version": "0.24.4",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -54,7 +54,7 @@
       ]
     },
     "@uniweb/kit": {
-      "version": "0.18.1",
+      "version": "0.18.2",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -82,7 +82,7 @@
       ]
     },
     "@uniweb/runtime": {
-      "version": "0.19.4",
+      "version": "0.19.5",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -110,7 +110,7 @@
       "deps": []
     },
     "@uniweb/templates": {
-      "version": "0.12.3",
+      "version": "0.12.4",
       "path": "framework/templates",
       "deps": []
     },