@aduptive/strapi-blockscene 2.0.0-alpha.12 → 2.0.0-alpha.13

package/README.md

@@ -29,6 +29,9 @@ module.exports = {
     config: {
       previewBaseUrl: '/block-previews',
       previewVersion: '2026-09-22', // optional cache buster appended as ?v=
+      // Optional: only these Strapi component folders get cards in Settings > Block gallery.
+      // Dynamic Zone insertion still follows each content type's own schema.
+      settingsComponentCategories: ['blocks'],
       components: {
         'blocks.hero': {
           label: 'Hero banner',
@@ -37,6 +40,7 @@ module.exports = {
           tags: ['Editorial'],
           keywords: 'heading introduction',
           image: '/block-previews/hero.png',
+          showRowThumbnail: false, // optional per-component row thumbnail
         },
       },
     },
@@ -259,8 +263,10 @@ opening or closing the row. The sources are the same as the gallery cards,
 minus the wireframe: a block with no image shows nothing, so nothing new is
 invented for blocks that were never captured. The thumbnail is inserted into
 Strapi's own header through the DOM (no Content Manager patch) and is
-restored when Strapi re-renders the list. Turn it off with the editor option
-`showRowThumbnails: false`.
+restored when Strapi re-renders the list. Configured OPEN and CLOSE group
+markers hide it by default. Override any component with
+`components[uid].showRowThumbnail` in code or on the Settings page, or turn all
+row thumbnails off with the editor option `showRowThumbnails: false`.
 
 ## Row actions
 
@@ -532,6 +538,11 @@ Minimal configuration:
    blocks, 0 when none or not editable); while it is positive the page may show
    a Paste button in its seams that sends `{ type: 'paste', after }` (a block
    key, or `null` for the start). Both are optional.
+   `update-page` also carries the complete live `entry`, including unsaved
+   values, plus `contentType` metadata and the projected zone name. New schema
+   fields therefore reach the frontend automatically; the frontend decides how
+   each field affects its page. The normalized `blocks` array remains alongside
+   it for visual editing and block-level actions.
    Keep the origin check (`admin` query parameter or your own constant).
 2. Allow the admin origin to embed it (`Content-Security-Policy: frame-ancestors`)
    and allow the page origin in the Strapi admin CSP (`frame-src`).
@@ -543,12 +554,16 @@ Minimal configuration:
    other one and the page then never hydrates, so `ready` never arrives and
    the pane reports the preview as unavailable with no error in either console.
 
-The bridge only exposes what the schema allows: attributes marked `private`
-are never projected, focused or edited; media URLs are passed through for any
-http(s) host (S3/CDN providers included) and same-origin paths; the zone shown
-is the first Dynamic Zone the user may read, and editing additionally needs the
-update permission on it. Pending dialogs are dropped when the document or
-locale changes.
+The bridge only exposes what the schema and the current user's read permissions
+allow. Attributes marked with Strapi's `private: true`, passwords, and
+attributes with `pluginOptions.blockscene.private: true` are never projected,
+focused or edited; the Blockscene option is useful for keeping a field out of
+the preview without changing its public API behavior. This privacy rule also
+applies inside components. Media URLs are passed through for any http(s) host
+(S3/CDN providers included) and same-origin paths; the zone shown is the first
+Dynamic Zone the user may read, and editing additionally needs the update
+permission on it. Pending dialogs are dropped when the document or locale
+changes.
 
 Editing from the page: plain-text areas the page explicitly maps
 (`data-block-field` + `contenteditable="plaintext-only"`) send `edit`. In the
@@ -1278,6 +1293,7 @@ uploads share an origin.
 - `tests/`: runnable regression checks.
 - [Local integration tests](docs/LOCAL-TESTING.md).
 - [Release checklist](docs/RELEASE.md).
+- [Prioritized roadmap](docs/ROADMAP.md).
 
 This plugin does not require Image Optimization; both can be installed together.