I’d love to request the ability to define allowed content per Component Slot in Bricks.
At the moment, Component Slots are a great step toward more flexible and reusable systems. However, when editing a component instance, users can still choose from a broad range of elements/components. For agency workflows, team setups, and client editing, this creates too much freedom and increases the risk of inconsistent layouts.
Please allow component authors to define which elements or components are allowed inside a specific slot.
For example, a slot could be configured to allow only:
-
certain basic elements, such as Heading, Text, or Button
-
specific Bricks Components
-
components from a defined category
-
a limited number of inserted items
This would make slots much safer and more useful for structured page building.
A very strong alternative to restricting slot content would be a classic repeater approach, similar to what users know from ACF, but as a property-type.
When creating a component property, alongside property types like Text or Image, there could be a new option: Component Repeater
This repeater property would allow the component author to define a repeatable child structure inside the component. For example, a component could contain a repeater area for: FAQ items, feature cards …
I’d love to discuss this further with others: should Bricks solve this through restricted slots, a repeater property, or both? If we can agree on a strong shared solution, I’d be happy to add it to the Idea Board.