riverbankcms 0.19.0 → 0.20.0

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