Currently, component slots only work inside the Bricks builder, but not in Gutenberg (tested in 2.2-RC2).
This makes it difficult to build nestable, client-editable components when content editing happens in Gutenberg instead of Bricks.
Examples that are currently hard or impossible to implement cleanly:
- Accordions with multiple items
- Nested lists
- Tabs
- FAQs
- Icon lists
- Any repeatable child structure inside a component
Slots solve this problem for developers inside Bricks, but since they are not available in Gutenberg, clients cannot use them.
A repeater property for components could provide an alternative solution that works in Gutenberg and allows users to add/remove structured items inside components.
This would make components significantly more useful in real-world client workflows where Gutenberg is used for content editing.