-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested Blocks: Inner block arrangement options #5448
Comments
The InnerBlocks component link are broken : |
@robbisy The component has been moved to the editor directory. Here's the updated link: https://github.com/WordPress/gutenberg/tree/master/editor/components/inner-blocks (I've revised the original comment as well) |
Closing this as Nested / Inner blocks have been updated https://github.com/WordPress/gutenberg/tree/master/editor/components/inner-blocks cc: @aduth |
Link is broken again :( |
@jessicaplant Here's the updated link. I expect this one should remain relatively stable (famous last words): |
Previously: #2995 (#2995 (comment)), #3745 (#3745 (comment))
The
InnerBlocks
component, used for block nesting, should allow a block implementer to assign a predefined block arrangement, optionally locking or otherwise restricting the types of blocks which are available for insertion in the block.This could potentially align with existing block templating
Pseudo-code examples:
For the inverse relationship (blocks restricted to certain parent contexts), we could either...
isPrivate
API (already used to omit block from inserter) and treatallowedBlockNames
as overriding this preferenceallowedRootBlockNames: [ ... ]
Related Work:
Discussion by @jorgefilipecosta about defining inner blocks supported:
https://wordpress.slack.com/archives/C02QB2JS7/p1520252046000229
cc @jorgefilipecosta
The text was updated successfully, but these errors were encountered: