Making Gutenberg viable with real world strategies
Thanks for Coming!
Problem 1:
Custom Blocks are Hard to Build
Problem 2:
We need to control what blocks can be used
Hide them and guide them
Gutenberg Block Manager plugin
https://wordpress.org/plugins/block-manager/
Problem 2:
We need to control what blocks can be used
Lock down those blocks!
Problem 3:
We need to control where blocks can be used
Problem 3:
We need to control where blocks can be used
Problem 3:
We need to control where blocks can be used
InnerBlocks in action
Columns
Column
<InnerBlocks />
Column
<InnerBlocks />
Required Block Settings
-
Block Name:
'my-blocks/page-content'
(can be anything, as long as it matches what you used in your template) -
multiple: false
(only one of these per page)
InnerBlocks Settings
-
template: [ 'core/paragraph' ] -
templateLock: false -
allowed_blocks: Any blocks that you want to be allowed in this section
Post-Presentation Update:
Between the time I recorded the WPCampus presentation and the time I delivered it,
I learned that the “Group” block (core/group) supports the templateLock
property, and it can be set to override the templateLock value of its parent.
If you wanted to create the page layout from our example, but do not need to restrict the Flexible area to specific blocks, there is no need to use a custom block. You can use this template setup instead:
Post-Presentation Update:
This will allow you to lock the position of the main content blocks, but the group block will be unlocked, essentially creating a new content editor nested inside your template.
Problem 4:
There are too many configuration options
Turning off custom fonts and colors
