THis is absolutely useful, infact i'm using the combination of custom element, classes, attributes, and components to create a nav bar that i can reuse on all of my projects, i often found myself using multiple variations of navbars on 1 website, so i think this combination is game changing, and after slots it'll be much efficient and powerfull. but i gotta say that the way you create your components, is a whole guru level🔥, fantastic job. I wish i could get a clonable of this
Brilliant but I wish you could attach the code to the page head instead of embedding a code block. Oh well. Thanks for the tip, this answered a question I was researching for quite a while now :)
Thanks for making this Sam. Could you reference the colors you've laid out in Webflow's variables in your custom code? I'm thinking it might be weird to have colors defined in Webflow's variables and then the same or similar colors defined separately in custom code. It terms of organisation/consistency I can imagine myself updating one but forgetting to update the other, etc.
Downside of classes is that client might decide to Clear unused styles, that will break every component based on this. Unless component stored somewhere dismembered with all additional classes applied. Nevertheless I use classes more over attributes, since it's more native.
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
I really like these features. Always best to limit what clients can mess with. Thank you Sam for explaining it so well too!
My pleasure!
THis is absolutely useful, infact i'm using the combination of custom element, classes, attributes, and components to create a nav bar that i can reuse on all of my projects, i often found myself using multiple variations of navbars on 1 website, so i think this combination is game changing, and after slots it'll be much efficient and powerfull. but i gotta say that the way you create your components, is a whole guru level🔥, fantastic job. I wish i could get a clonable of this
When it’s done it’ll be cloneable 👍
Brilliant but I wish you could attach the code to the page head instead of embedding a code block. Oh well. Thanks for the tip, this answered a question I was researching for quite a while now :)
Love this! Do you have a cloneable project for this with the code included? Thank you ❤
This was very cool! Thanks for sharing Sam
Thanks Brendan! 👍🏻
Amazing, looking forward to learning more from the cloneable 🔥
are you using Lumos Framework in this?
Thanks for making this Sam. Could you reference the colors you've laid out in Webflow's variables in your custom code? I'm thinking it might be weird to have colors defined in Webflow's variables and then the same or similar colors defined separately in custom code. It terms of organisation/consistency I can imagine myself updating one but forgetting to update the other, etc.
Where can I get your blueprint code from?
2027: "webflow now lets us style elements without using the native site builder! All you need is html, css and javascript!!!"
Downside of classes is that client might decide to Clear unused styles, that will break every component based on this. Unless component stored somewhere dismembered with all additional classes applied.
Nevertheless I use classes more over attributes, since it's more native.
I like to include the classes within a style guide page so that they are safe from being accidentally cleared 👍🏻
Subscribing ☮️
Thank you 🙏🏼