@amplifyup/sdk 0.1.34 → 0.1.36

package/README.md

@@ -2,7 +2,7 @@
 
 Official JavaScript SDK for [AmplifyUp](https://amplifyup.ai) — event tracking, Edge-resolved page layouts, personalization, and Composer preview on your site.
 
-**Full guide:** [docs/sdk-site-setup.md](../../docs/sdk-site-setup.md)
+**Full guide:** [Developer docs](https://amplifyup.ai/docs/developers) · [API](https://amplifyup.ai/docs/api)
 
 ## Install
 
@@ -86,8 +86,36 @@ Field names must match the component registry in AmplifyUp. Connect CMS document
 | Production visitors | Edge `/v1/resolve` | Default |
 | Next.js SSG / ISR | Edge `/v1/routes` then `/v1/resolve` | `generateAmplifyStaticParams` + `fetchPageConfigServer` |
 | Composer preview | Orchestrator layout provider | `?preview=true` / Composer iframe |
+| Runtime queries | Edge `/v1/query` | `queryContent` — search, load more, pickers |
 
-The SDK maps Edge’s resolved tree into `layoutTree` and renders it. Edge already applies personalization and CMS projection — the site does not call CMS or Decision APIs for layout. Visitor-specific variants overlay the static HTML in the browser by default (`clientPersonalization`).
+The SDK maps Edge’s resolved tree into `layoutTree` and renders it. Edge already applies personalization and CMS projection — the site does not call CMS or Decision APIs for layout. After paint, the overlay calls `POST /v1/select` (or `selectVariants()`) then `/v1/resolve?variants=` so decisions stay on the edge (`clientPersonalization`).
+
+## Runtime queries
+
+Page resolve covers data known at Deploy. For data a visitor asks for — search, load more, a picker — use `queryContent`. The browser asks AmplifyUp, AmplifyUp asks your content source, so no CMS credentials or query syntax live in your site.
+
+Mark a query connection **paginated** in Composer and the list prop gains pagination meta, including the published query spec:
+
+```tsx
+'use client';
+import { queryContent, nextPageSpec, searchSpec } from '@amplifyup/sdk/react';
+
+// next page
+const more = await queryContent({
+  trackingId,
+  route: '/insights',
+  spec: nextPageSpec(postsPagination),
+});
+
+// search — keep `?q=` as input only; do not read searchParams on the server page
+const hits = await queryContent({
+  trackingId,
+  route: '/insights',
+  spec: searchSpec(postsPagination, 'title', term),
+});
+```
+
+Only entities published with that route can be queried, and visitors only see published content. Also available from `@amplifyup/sdk/server`. See the [runtime queries guide](../../docs/sdk-site-setup.md#8-runtime-content-queries).
 
 ## Track events