Why Your Webflow Class Stops Working Randomly

[@jdanielortega]

I can not believe such an important distinction is not mentioned anywhere else, as always thank you for unearthing these golden nuggets!

[@enzweikoo]

Awesome! Thanks. Your way of doing your thing is amazing. Greets from Germany

[@josuebonilla8495]

For a second I read broken glasses and thought “oh no”. Thanks for this!

[@jclewis33]

This is a great tip. Thanks for sharing.

[@PruthviPanchani]

Thank you!

[@_instantrush_]

Hey, I really, really enjoy watching your videos, and they are very educational and helpful. I haven’t been using Webflow for long, but I want to dive deeper into it, and your Lumos V2 is super interesting. I have a question: To use Lumos, do I need to open the cloneable for each project and then start from there? Or how exactly should I go about it? Also, do I always need to purchase a site plan to use Lumos?

[@timothyricks]

Thank you for the kind words and for wanting to try Lumos! Yes, it’s best to start each new project from a fresh copy of the Lumos cloneable to make sure you have the latest version. Currently, color themes are set in custom code until Webflow supports that natively so it would require a site or workspace plan to edit the custom code for that part of Lumos. I have a full tutorial on starting a project from scratch with Lumos here. kzbin.info/www/bejne/p4KUmmmAlNiEhrMsi=obRdOZmeWBKqVkn9

[@_instantrush_]

@@timothyricks Thank you very much for the quick and helpful response. Do you perhaps have a few more tricks or good tutorials to really get started with Webflow? I’ve watched all the videos from Webflow University and many from you, but the way you do it seems a lot more complicated, yet it makes much more sense and also looks better.

[@timothyricks]

@@_instantrush_ Sure thing! I made this crash course recently for getting started in Webflow. kzbin.info/www/bejne/fZXIgn59nbV-prM

[@_instantrush_]

@@timothyricks Thank you very much for the tutorial and the quick response.

[@atakann]

Cool

[@DANNYFIGDESIGNS]

🤗

[@RicardoAum]

is there a way to delete classes that are this simple and I missing?

[@timothyricks]

There's the Clean Up feature under the Style Selectors tab in the designer. It removes any unused classes.

[@BradfordHuber]

why not just set utility classes as !important?

[@timothyricks]

Custom classes wouldn’t be able to override them when we need to override a style in a certain state or breakpoint. Also, !important can only be applied through custom css properties so we’d lose a lot of the native ui. (For example, setting display: grid or flex through custom properties hides the alignment settings in the ui). And also, we’d still run into issues with utilities conflicting with each other if all or most of them have !important. It’s best to set everything in the right order and avoid !important.