Hi everyone,
The ability to create Gutenberg blocks from Bricks Components is a great step forward, but in its current form it feels very limited for real-world client sites without InnerBlocks support.
We currently use GutenBricks for this, and it works well. However, I would expect Bricks to eventually support some form of InnerBlocks, slots, or a similar content area system so clients can add native Gutenberg elements inside these component-based blocks. That would make the feature much more practical and flexible for real-world use cases.
To make it even more complete, it would be great to see support for ACF-style fields as well, especially for repeater and relationship fields. This would open the door to building more advanced and reusable blocks while still keeping the workflow inside Bricks as much as possible.
Our current workflow is:
-
Create the blocks using GutenBricks.
-
Add a custom frontend stylesheet.
-
Add a custom backend/editor stylesheet.
-
Use those styles to handle widths, gaps, spacing, and Gutenberg element styling.
-
Match Gutenberg elements visually with our Bricks/CSS framework styling.
Even if this custom CSS workflow remains necessary, we would still prefer to rely more on native Bricks Components. At the moment, the lack of InnerBlocks support makes that difficult and keeps the feature from being fully usable for more flexible client-managed layouts.