Proposal: Block Instance Reuse and Block Control Center for Layout Blocks #15945
minimalimited
started this conversation in
Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Proposal: Layout Block Editing Utilities
This proposal introduces two complementary features designed to improve editorial workflows when working with layout blocks in Payload CMS.
Large Payload projects frequently reuse the same block types across many pages. These features aim to make it easier to manage and reuse those blocks without disrupting Payload’s document-based architecture.
Block Control Center
The Block Control Center is an admin utility that allows editors to locate and edit layout block instances across all pages from a single interface.
Instead of navigating page by page to find a specific block, editors can select a block type and view every instance of that block used across the website.
The interface is structured in three main areas:
Block Type Selector
Allows the editor to choose a block type currently used in the site.
Instance List
Displays all pages where that block appears.
Instance Editor
Renders the selected block using the same field UI used in the page editor.
When an instance is edited and saved, the change is applied through the parent page document. This preserves Payload’s existing hooks, versioning system, and revalidation behavior.
This approach allows teams to manage reusable content structures more efficiently while maintaining Payload’s document-based architecture.
Copy Block From Another Page
The Copy Block From Another Page feature allows editors to reuse the structure and content of an existing block instance when creating a new block.
When working with layout blocks in Payload CMS, the same block types are frequently reused across multiple pages, such as Call To Action sections, content blocks, or promotional components.
Currently, editors must manually recreate block configurations or copy content field by field when reusing a block. This process can be time-consuming and increases the risk of inconsistencies between pages.
The proposed feature introduces a simple workflow that allows editors to duplicate the configuration of an existing block instance directly from the block menu.
UX Flow
When the content is copied, only the editable field values are transferred. System fields such as IDs, timestamps, and internal metadata are ignored.
The resulting block remains completely independent from the source instance, meaning editors can freely modify it without affecting the original block.
This feature significantly improves editorial efficiency by allowing teams to reuse existing block configurations quickly while maintaining Payload’s flexible block-based architecture.
Beta Was this translation helpful? Give feedback.
All reactions