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. ua-cam.com/video/2Ycl4Yh5n98/v-deo.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.
![Lp. Последняя Реальность #107 РОДНОЙ ДОМ [Финал] • Майнкрафт](http://i.ytimg.com/vi/IK3QKzKUlHM/mqdefault.jpg)
You're a machine Tim.
I'm basically learning about new updates from you before I even get the notification from Webflow.
Me to 😀 honestly I got kind of lazy reading through release docs, because Tim will explain it better in a much more consumable form 🙂
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!
This is actual insanity and I'm so excited for it! I hope we get a new Components Panel soon so we can better organize all of our components
An updated Components Panel would be extremely helpful! I have a wishlist a mile long for components 😂But slots unlocks a lot!
Great video as always!
The face you made when you mentioned marketers describes the struggle 🤣
Really happy to see this feature finally out!
So good! Thanks for sharing, Tim!
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. ua-cam.com/video/2Ycl4Yh5n98/v-deo.html
@@timothyricks Awesome! I`ll check it out for sure. I just started with Webflow and I`ll be binge watching your channel haha Thank you!
Awesome wrap up Tim!
Thank you!!
The goat
Are the component slots available in the editor view? Would be nice so marketing can have access to the editor with cms and components?
Not today but it will come with the new marketer mode (Page Building) coming later this year I think
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.
Like Figma
This is particularly useful for devlink, no? Can create action-based components that then contain functionality, then lego them together.
I haven't worked with devlink, but it sounds like it would be a good use case for slots.
They nuked devlink smh