@se-studio/project-build 1.0.120 → 1.0.122
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.
package/CHANGELOG.md
CHANGED
package/package.json
CHANGED
|
@@ -18,9 +18,8 @@ Use **set** for scalar and link fields; use **rtf** only for rich text fields.
|
|
|
18
18
|
|
|
19
19
|
- **Append** an embedded entry: `cms-edit rtf embed @c1 body <entry-id>`
|
|
20
20
|
- **Insert** at position: `cms-edit rtf embed @c1 body <entry-id> --at 0`
|
|
21
|
-
- **
|
|
22
|
-
- **
|
|
23
|
-
`cms-edit rtf embed @c1 body <asset-id> --asset --at 12 --align center --width-percent 40`
|
|
21
|
+
- **Raw asset** embed: `cms-edit rtf embed @c1 body <asset-id> --asset` — inserts an `embedded-asset-block` with **no** width/alignment on the block (Contentful only allows `data.target`).
|
|
22
|
+
- **Width / horizontal position:** use a **Media** entry (not `--asset`). Create one with `cms-edit create media --asset-id <id> --name "…" [--position Middle] [--width 40]` (prints the new entry ID; does not replace your session), then `cms-edit rtf embed @c1 body <media-entry-id> --at 12`. Or set fields in the Contentful app. Same image, different layout in two places ⇒ two Media entries pointing at the same asset.
|
|
24
23
|
|
|
25
24
|
Editing or moving existing embeds is **not supported in v1**.
|
|
26
25
|
|