Thank you so much! I'm really glad this helps

My pleasure!

section - container -layout. Set defaults in your embed plus the ability to override these defaults in Webflow. Thank you!

Haha, thank you!!

Thanks so much for watching!

@@timothyricks Any way you can give your community members a cloneable with all the mentioned with all the default styles

Awesome! Thanks so much

Thanks so much, Austin! I’m really glad this helps, and thank you for the suggestions! Setting defaults and using utility classes are probably the biggest tips for reducing css bloat. I’ve packed all of my recommended defaults and utilities into the Lumos V2 cloneable. webflow.grsm.io/tricks?path=lumos-v2-beta

Haha, thank you!

Thanks so much for the idea! I’m experimenting with maybe including a few common components in the Lumos cloneable to use as a starter. Currently, I believe Webflow duplicates the variables when copying a section between projects so that would likely have to be solved first before creating an external library

I thought the same thing until doing more research recently! If html ever adds a "container" attribute one day, it could interfere with our custom attribute. So custom attributes are supposed to start with data- to avoid conflicts

@@timothyricks Is the only concern here that html might add an official attribute with the same name or are there other reasons to use data- in attribute names. I'm creating an internal gsap library using attributes and adding data to each attribute name would slow down applying them to elements but I also want to avoid future issues. I'm guessing if an attribute name is specific enough eg: gsap-load the likelihood of it conflicting with future html is little to none. Whereas using container definitely has a lot higher likelihood...

@@calebraney Good question! I think that was the main issue. They mentioned html validators won't know if the attribute was an error or intentional without the data- and also without the data- it has a higher likelihood of competing with other people's code. But I'm not sure if either are big issues for Webflow builds. stackoverflow.com/questions/24932391/are-custom-html-attributes-without-data-prefix-a-valid-attribute

Hi Harry, the custom element allows us to set inline styles and link class names to component fields if needed. This is usually more needed for sections than main or articles, but on the published site, there’s no difference between using webflow’s default elements or a custom one with the same tag. The custom ones just give us more features

Thank you! I don’t know. I’ve heard a few success stories but never tried it

Hi! No, this is a framework I created called Lumos. kzfaq.infoPekd3KVtqQo?si=6NxvDqw8d9M39cKS

Thanks so much for the idea! I cover this in my full build tutorial but definitely should make a shorter video on it. kzfaq.infonj-1qB47aKo?si=-VH6hSay44_8UvOz

@@timothyricks Oh, excellent! Thank you Timmothy Ricks :)

@@timothyricks I'll take a look at this video, but if you did make a little digestible naming and organization video for beginners, I would 100% be your target market

Hi, good question! Usually, we'd want background colors or images to be applied to our sections, not to the containers, so that it can span the full width of the screen.