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!
Thank you for the video! I do feel that the way webflow has implemented component variations doesn't feel super intuitive and is more difficult to use than it should be. I really love the way figma does components and variables where you can easily just update images and text to make variables of components but go back to your main component to make updates that affects all the variants except for the parts that have been updated on the variants. I wish that webflow would implement the way figma does most things cause it feels very intuitive!
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. ruclips.net/video/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.
After a long deep dive, I've come to the conclusion that Slots are almost completely redundant. Certainly in their current form. In fact on balance they seem a net negative, particularly when thinking of the type of site created in Webflow. Other than a few limited use cases, it will only mean more complication/layers of abstraction, endless nesting, an unreadable site structure, a never ending component panel (chock full of single use components) & unless you remember all your classes, a total non starter. Feels very gimmicky tbh, not sure where Webflow is going these days.
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!
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 🙂
Thank you for the video! I do feel that the way webflow has implemented component variations doesn't feel super intuitive and is more difficult to use than it should be. I really love the way figma does components and variables where you can easily just update images and text to make variables of components but go back to your main component to make updates that affects all the variants except for the parts that have been updated on the variants. I wish that webflow would implement the way figma does most things cause it feels very intuitive!
Great video as always!
The face you made when you mentioned marketers describes the struggle 🤣
Really happy to see this feature finally out!
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. ruclips.net/video/2Ycl4Yh5n98/видео.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!
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!
Awesome wrap up Tim!
Thank you!!
So good! Thanks for sharing, Tim!
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.
i need to learn more about components ? The only thing i use it for is my Nav bar
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
The goat
After a long deep dive, I've come to the conclusion that Slots are almost completely redundant. Certainly in their current form. In fact on balance they seem a net negative, particularly when thinking of the type of site created in Webflow. Other than a few limited use cases, it will only mean more complication/layers of abstraction, endless nesting, an unreadable site structure, a never ending component panel (chock full of single use components) & unless you remember all your classes, a total non starter. Feels very gimmicky tbh, not sure where Webflow is going these days.
I gotta say...I have no idea what's going on anymore lol
I didn't understand why is this useful