Hey Timothy I have been using lumos for a while now and it’s been going really good. I just had an issue with attribute names which show up in props of a component (using lumos extension I believe), sometimes it shows up and most of the times it doesn’t, I have to manually type things. Is it a problem from my end? If so any idea how I can resolve it
Thank you for the feedback! I've received feedback of other Webflow Extensions conflicting with this one. Do the component buttons show up every time you refresh Webflow, or do sometimes the component buttons not display on refresh?
@@timothyricks when I refresh the site sometimes it works. Btw I don’t have any other webflow extensions installed I am using arc browser just for info!
Remembering shortcuts doesn't come naturally to me, and I avoided them for a long time. In Webflow, they're very important for efficiency though. When I picked one or two to focus on at a time, it eventually became second nature. The most important one by far is quick find.
Have you moved on to just add custom code (styling) in your code embed component and drop it across all pages? Do you only reserve the and custom code inputs for JS?
Yes, I usually keep css in an embed on the page so we can see the results of the css without having to publish our site. The "Custom Code" Component goes on every page and holds css that applies to the site as a whole. Component-specific CSS can go in an embed inside the related component to make it easier to find and edit later. Component-specific JavaScript can also go in an embed inside the related component so it's not loaded on pages that don't include the component and also follows the component if we ever add it to a different page later. Site Settings holds any JavaScript that applies to every page of the site, and Page Settings code is rarely used. lumos.timothyricks.com/docs/faqs#where-should-custom-css-be-added
The Opacity Shortcut 🤯 Great Value once again - thank you!!
Thanks so much! I'm glad that one helps!
I love you! Great work!
Today was trying to understand the strategy and the process. Thanks for your explanation 🎉
Hey Timothy
I have been using lumos for a while now and it’s been going really good.
I just had an issue with attribute names which show up in props of a component (using lumos extension I believe), sometimes it shows up and most of the times it doesn’t, I have to manually type things.
Is it a problem from my end? If so any idea how I can resolve it
Thank you for the feedback! I've received feedback of other Webflow Extensions conflicting with this one. Do the component buttons show up every time you refresh Webflow, or do sometimes the component buttons not display on refresh?
@@timothyricks when I refresh the site sometimes it works.
Btw I don’t have any other webflow extensions installed
I am using arc browser just for info!
So useful! Thank you for creating this !
Thank you, Skylar!
Could Lumos Extension purge the unused classes when saving or publishing?
Thank you so much for this.
Another game changer.
Thank you for the kind words! :)
Loving the Lumos vids. Any plans to upload a few more full page builds?
Thank you! Yes, I plan to do more full builds in the future. Just making sure I have the fundamentals well documented first
Big respect to people who can remember shortcuts and key combos, it aint me tho fam
Remembering shortcuts doesn't come naturally to me, and I avoided them for a long time. In Webflow, they're very important for efficiency though. When I picked one or two to focus on at a time, it eventually became second nature. The most important one by far is quick find.
Have you moved on to just add custom code (styling) in your code embed component and drop it across all pages? Do you only reserve the and custom code inputs for JS?
Yes, I usually keep css in an embed on the page so we can see the results of the css without having to publish our site. The "Custom Code" Component goes on every page and holds css that applies to the site as a whole. Component-specific CSS can go in an embed inside the related component to make it easier to find and edit later. Component-specific JavaScript can also go in an embed inside the related component so it's not loaded on pages that don't include the component and also follows the component if we ever add it to a different page later. Site Settings holds any JavaScript that applies to every page of the site, and Page Settings code is rarely used.
lumos.timothyricks.com/docs/faqs#where-should-custom-css-be-added
@@timothyricks Thank you Tim! All of this makes total sense and is so much more effective.
Thank you! I’m so glad to hear that
Goldmine 🎉