riverbankcms 0.19.0 → 0.21.0

package/dist/cli/init-docs/content/getting-started.md

@@ -166,3 +166,30 @@ If local content includes unrelated differences, see `workflows/agent-safe-sync.
 1. Read `cli-reference.md` for detailed command documentation
 2. Review `schema.md` to understand this site's content model
 3. Check `workflows/` for step-by-step guides
+
+
+## Customer portal routes
+
+When portal auth is enabled, `riverbankcms init` generates these reserved routes:
+
+| Route | SDK helper | Scaffold template |
+| --- | --- | --- |
+| `/portal` | `createPortalPage` from `@riverbankcms/sdk/next` | `portalPageTemplates` |
+| `/portal/tickets/[registrationId]` | `createPortalTicketPage` | `portalPageTemplates` |
+| `/portal/digital-products/[entitlementId]` | `createPortalDigitalProductPage` | `portalPageTemplates` |
+| `/portal/digital-products/[entitlementId]/files/[assetId]` | `createPortalDigitalProductFilePage` | `portalPageTemplates` |
+| `/api/portal/callback` (GET) | `handlePortalCallback` from `@riverbankcms/sdk/portal` | `portalCallbackRouteTemplate` |
+| `/api/portal/logout` (POST) | `handlePortalLogout` | `portalLogoutRouteTemplate` |
+
+Existing sites should add these files after upgrading the SDK. Import
+`@riverbankcms/sdk/styles.css` globally. The page helpers provide the site theme
+scope automatically; sites with `themeSource: 'local'` pass the same `theme`,
+`themes`/`themeSwitch`, or `getTheme` options used by their catch-all. A custom
+resolver receives `content.type === 'portal'` and `content.site` on these routes. The callback and logout routes own the HTTP-only cookie.
+The file route authenticates before redirecting to a signed download URL.
+
+For a custom host, `CustomerPortal` from `@riverbankcms/sdk/portal/client` takes
+`siteId`, `apiBaseUrl`, `portalToken` (nullable), `demoEmailSuppressed`, plus optional `callbackPath`, `logoutPath` and `bookPath`
+(defaults `/api/portal/callback`, `/api/portal/logout`, `/book`). Wrap it in the
+site's `ThemeScope`. This is a reserved route component, not a CMS block.
+`@riverbankcms/sdk/portal` remains the server helper entry.

package/dist/cli/init-docs/content/workflow-content-types.md

@@ -328,3 +328,28 @@ riverbankcms delete entry <content-type> <identifier> --yes
 - Verify `titleField` matches an existing field `id`
 - The field must be a text field
 - If not set, defaults to `'title'`
+
+### Entry links and singleton identifiers
+
+Entry fields with `type: 'link'` use the same link objects as blocks:
+
+```json
+{
+  "buttonLink": { "kind": "page", "identifier": "start-a-project" },
+  "subLinkLink": { "kind": "external", "href": "https://example.com" }
+}
+```
+
+Use `kind: 'url'` with `href` for a relative URL such as `/contact`.
+Legacy URL strings are normalized to that object when read or published.
+SDK inferred link fields use `LinkValue | null`; new content should use objects.
+
+A singleton has one entry. Config sync creates it with identifier
+`<content-type-key>-singleton`. Run `riverbankcms pull entries <content-type-key>`
+(with `--env=remote` for the remote environment) and edit the resulting file.
+Use the pulled identifier in both the JSON `identifier` and any identifier
+argument to `riverbankcms push entries`. Push does not retarget another identifier:
+a mismatch fails with a message naming the existing singleton identifier, before
+writing the entry. A filename alone does not rename an entry.
+
+Resolve entry link objects with the SDK's `resolveLinkHref(link, context)`, using the same route/stage context as block links.