Components have been one of the most powerful additions to Bricks, but also one of the biggest pain points for many users since they were introduced.
I’d like to start a dedicated thread where everyone who has used Components extensively can share their real-world experience — especially those working with:
nested components
slots
variants
repeatable / reusable layouts
client-editable setups
larger production sites
edge cases and complex component structures
The goal is not to complain for the sake of complaining, but to collect useful, practical feedback in one place so the Bricks team has a clear improvement list from users who are actually pushing Components in real projects.
Please share:
What works well for you
What feels confusing or unintuitive
Bugs you’ve encountered
Limitations that slow you down
Suggestions for how Components could be improved
Any workflows or patterns you’ve found that make Components easier to manage
Components have huge potential, but for them to become truly reliable and enjoyable to use, the feedback needs to come from users who have spent real time with them.
Hopefully this thread can become a constructive reference point for future improvements.
That’s also possible, but it’s not the first or best choice. This is presented somewhat ambiguously in the documentation—we’ll take care of it.
All you have to do is create a toggle property, link it to the “hide element” settings, and then you can show or hide the element on a per-instance basis.
Alternatively, you could certainly use variants and hide the elements using CSS display: none.
The difference from the “hide element” settings is that the elements are still included in the markup; they are simply invisible. With “hide element,” they aren’t rendered at all.
I tested components on a new website for a client and it’s great, congratulation to the Bricks team. It’s easier to edit for the client and manage for us. I love the feature to enable them for Gutenberg. Anyway 2 things could be improved I think :
Restricted slots : When we use slots for clients, it would be great to be able to restrict the slot for certain components or widget. (for example, certain basic elements, such as Heading, Text, or Button or specific component)
Components repeater : This repeater property would allow the component author to define a repeatable child structure inside the component. For example, the repeater property would be great for listing or FAQ slots.
Be able to rename or reorder Component Categories.
I don’t know if this is the intended behaviour - but when I unlink a component that has variants it reverts to the last created variant.
E.G. i create a base component and then a variant with background red. I place a base component on the canvas but then if I unlink this component it defaults to the red variant, it does not maintain the selected base or other previously created variants.
It would be helpful if when unlinked the component could maintain its selected variant.
