Compile editable designs into constrained native InnerBlocks - #11
Merged
noeltock merged 1 commit intoSep 4, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A reusable block is still a poor WordPress citizen if headings, images, links and buttons become bespoke fields or frozen HTML. The design needs to stay intact without replacing the editor behaviour WordPress already provides. Closes #4.
Solution
Generate a thin custom wrapper around one native
InnerBlockstree. Ordinary content remains in Core Heading, Paragraph, Image, List, Buttons and Button blocks. The plan controls the template, direct-child allowlist, editability and locking, while fixed structure stays out of the outer block's content attributes.Testing and verification
The native-child, locking and content-only contracts are covered by the repository tests and the real WordPress lifecycle used by the current integration. The public verification record is the green CI run on Node 20, 22 and 24 with WordPress 7.1.
Risk and rollout
The static path does not generate arbitrary controls or dynamic rendering. Designs that cannot fit one native content region fail with a source-located reason rather than silently becoming custom HTML.