riverbankcms 0.22.2 → 0.23.0

package/dist/cli/init-docs/content/cli-reference.md

@@ -457,7 +457,7 @@ export default defineConfig({
 });
 ```
 
-**Status Sync**: Push automatically syncs draft/published status based on the `status` field in your local content files. If local content is "published" but remote is "draft", push will publish it. If local is "draft" but remote is "published", push will unpublish it.
+**Publication**: Page pushes save drafts, including block additions, deletions and order changes on already-published pages. A page file’s `status: "published"` never publishes pending work. Review the complete page draft, including dashboard changes, then use `riverbankcms page publish <identifier>` to publish all pending page content, structure, design and page details together. A local `status: "draft"` can still unpublish a published page. Content entries still take their draft or published status from your local files.
 
 ### settings booking configure
 
@@ -688,7 +688,7 @@ site style's defaults until a design is saved for it, for example with
 
 ### page publish
 
-Publish a page.
+Publish the whole page draft, including all pending content, structure, design and page details. Review changes saved in the dashboard as well as the CLI before publishing.
 
 ```bash
 riverbankcms page publish <identifier>

package/dist/cli/init-docs/content/content-management.md

@@ -436,7 +436,7 @@ export default defineConfig({
 | ----------------- | ---------------- | -------------------------------------------- |
 | `existingEntries` | `skip`, `update` | Whether to update entries that already exist |
 
-**Status Sync**: Push automatically syncs draft/published status based on the `status` field in your local content files. Set `"status": "published"` in a local file to publish on push, or `"status": "draft"` to unpublish.
+**Publication**: Page pushes save drafts, including block additions, deletions and order changes on already-published pages. A page file’s `status: "published"` never publishes pending work. Review the complete page draft, including dashboard changes, then use `riverbankcms page publish <identifier>` to publish all pending page content, structure, design and page details together. A local `status: "draft"` can still unpublish a published page. Content entries still take their draft or published status from your local files.
 
 ### Environment Cloning (Remote ↔ Local) Best Practices
 

package/dist/cli/init-docs/content/workflow-custom-block.md

@@ -54,9 +54,7 @@ export default defineConfig({
       category: 'content',
       icon: 'Workflow',
       tags: ['process', 'steps', 'flow'],
-      previewCustomize: {
-        quickFieldPriority: ['title', 'introText'],
-      },
+      promotedFields: ['title', 'introText'],
       fields: [
         {
           id: 'title',
@@ -91,7 +89,9 @@ export default defineConfig({
 });
 ```
 
-`previewCustomize` is optional. When present, `quickFieldPriority` must list one or more unique field IDs to consider for compact Preview Customize controls; unlisted fields remain in the full panel.
+`promotedFields` is optional. Promoted behaviour/data fields appear in “What it shows”, promoted appearance fields in “Look”, and content fields stay in “Text”. Remaining fields appear in “More settings”; there is no quick-field cap.
+
+A custom block or built-in block extension can also declare `lookField` with the ID of one of its own existing single-select fields. Its options become labelled Look tiles. This remains an ordinary content field on every editing surface, including the dashboard; it does not use built-in Default or pin behaviour.
 
 ### Step 2: Choose Field Types
 

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

@@ -72,20 +72,24 @@ riverbankcms page list --json
 
 To see everything with pending changes across all content types in one shot — correctly server-filtered, not capped by pagination — use `riverbankcms drafts` instead of scanning `entry list` page by page.
 
-## Bulk Publishing via Push
+## Push and Publication
 
-When using `riverbankcms push`, the status is synced based on your local content files.
+Page pushes save drafts. Adding, deleting or reordering blocks on an already-published page leaves the live page unchanged until you explicitly publish the whole page. A page file’s `status: "published"` does not publish it or any other pending page changes.
+
+Review the complete draft, including changes saved in the dashboard, then run `riverbankcms page publish <identifier>`. Publication includes all pending page content, structure, design and page details.
+
+Content entries still take their draft or published status from your local files.
 
 ### How Status Sync Works
 
-Push compares the `status` field in your local files to the remote status:
+For content entries, push compares the `status` field in your local files to the remote status:
 - If local is "published" and remote is "draft" → push will **publish** the content
 - If local is "draft" and remote is "published" → push will **unpublish** the content
 - If statuses match → no status change
 
-### Edit Local Files to Control Status
+### Edit Local Entry Files to Control Status
 
-In your local content files, set the status field:
+In your local entry files, set the status field:
 
 ```json
 {
@@ -101,6 +105,8 @@ Then push:
 riverbankcms push
 ```
 
+A page file with `status: "draft"` can still unpublish an already-published page. Use `riverbankcms page unpublish <identifier>` to do this explicitly.
+
 ### Push Then Publish Selectively
 
 ```bash