For us, slots were the last missing piece regarding Webflow components. Now everything can be a component, resulting in much more well-defined (and adhered to) design systems. Fantastic video, as always!
Oh boy, that was fast haha Thanks, Timothy! This is really a very very exciting feature. I'd be amazing if you could make other videos with some real world scenarios where slots could be used, just so we can see how to actually make it work in Webflow. It's a whole lot of nesting and passing props around, it can get very complicated. I subscribed to follow up on this, Thanks again!
Thanks so much! I released a video yesterday on how to create new components by duplicating a starter component so that the props don't have to be recreated each time. That's going to be vital if child components have many slots that need to be passed to the parent component. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-2Ycl4Yh5n98.html
This looks great but I'm concerned about performance of the Webflow Designer when creating too many components. My experience has been that the more components I create the more slowly the Designer operates. For reference, I am using an M1 Max w/ 32gb ram with a 2gig network. One more thing, I noticed that you are using rich text for both the heading and paragraph text in the card example. Are you using it so it's easier for someone to edit the content vs the small stock context windows within the component fields?
There's been significant improvements in Webflow Designer performance recently, but even before that, the designer ran smoothly for me when using a lot of components on an older intel-based macbook. The number of elements on a page might have a larger performance impact than the number of components.
