There are many cases where the content we want to place inside a Component Slot cannot be turned into a component. It would be preferable if any content can be placed in this slot, and not just components.
One example from my project is on a Collection Page for Case Studies I have a CMS Collection List Photo Gallery that I want to place inside of my "Box" Component, which is just a styled wrapper of content. I would use a Slot, but can't because the Collection List is linked to a property specific to that page, therefore I have to unlink my Component which definitely defeats the purpose of a Slot in the first place.
There's a lot of potential for Component Slots, and adding this would make them even more powerful!
Kevin Gerstner
.svg){kind=logo}
I wanted to add that this also could be a setting on the component slot, if you want to accept non-component content or not.
Absolutely agree! This limitation is one of the biggest barriers to using Component Slots effectively. Here are some additional compelling use cases that would be unlocked:
True Layout System:
Page templates with nav/footer components + flexible content slots
Section wrappers with preset spacing, backgrounds, and grid layouts
…
Design System Efficiency:
Utility components (cards, boxes, panels) that work with any content
Fewer micro-components cluttering the component library
Better maintainability - update layout logic in one place
Reduced component duplication for minor variations
Developer Experience:
Modern framework paradigms (React/Vue component children pattern)
Cleaner separation of layout vs content vs styling concerns
Faster prototyping - drop content into pre-built layouts
Better client handoff - non-technical users can add content to structured layouts
Real-World Impact: This would transform Component Slots from a nice-to-have feature into a core layout system that rivals modern development frameworks while maintaining Webflow's visual design workflow.
The current workaround of "componentizing everything" defeats the purpose and creates maintenance nightmares. This enhancement would unlock Component Slots' true potential!
Yes! I often have the case where I would like to place content in a component which is just a slight variation of an element or sub-component, but would definitely not warrant becoming a new component in itself as otherwise the components library would become a bloated mess over time.