Importing Lumos Into Older Projects Using Webflow Libraries

Поділитися
Вставка
  • Опубліковано 17 жов 2024

КОМЕНТАРІ • 42

  • @oyebolaopeyemi8590
    @oyebolaopeyemi8590 2 місяці тому +3

    Dudee...at this point, you're just reading our mind. I literally searched for this at the beginning of this week. Recently learning to use Lumos. Got a project where someone wanted me to help with adjusting his website responsiveness, spacing consistency and all. Decided to go through a more complex route of using this opportunity to learn Lumos framework. After using the FAQ section of your website to find out how to do it, I realised I'll need to use a cut and copy app to import variables but I'll still need to create the components manually. Though I could copy the components over but it would be detached and I'll have to manually configure it back. It was a tasking procedure at the beginning but I've started getting the groove of the framework and I'm experiencing the blessings of it. Though there are still areas that I'm not fully clear on, I'm getting a better understanding by directly using it in a project

    • @timothyricks
      @timothyricks  2 місяці тому +2

      This is so great to hear! Thank you for trying Lumos! I'm glad that this process is much easier now. Hopefully by rebuilding some of those components before though, it gave you a greater understanding of how everything works.

    • @oyebolaopeyemi8590
      @oyebolaopeyemi8590 2 місяці тому

      @@timothyricks yes, thanks a lot. It gave me a greater understanding of components in general and with the way it works in Lumos. You've been a great help in the Webflow community.

  • @matthewstark9062
    @matthewstark9062 4 дні тому

    Hey Timothy, just wondering if you could create a guide for upgrading from an older version of Lumos to a newer one. I am trying to import all 2.05 variable changes (specifically u-block-gap), style guide changes and custom code changes without overriding my current variables and breaking parts of the site. Is this possible? I am struggling to track changes and see what I need to update when brining over new variables. A bunch of my heading font-sizes seem broken, but I have no idea how to fix them.

  • @kenneth_yu
    @kenneth_yu 2 місяці тому +3

    I am trying to figure out when you had time to record this...

    • @timothyricks
      @timothyricks  2 місяці тому +2

      This morning in the hotel! 😂 That’s why the audio sounds so bad

    • @kenneth_yu
      @kenneth_yu 2 місяці тому +2

      @@timothyricks my mind cannot comprehend your level of output 🤯

  • @itstoelean
    @itstoelean 2 місяці тому

    A few weeks ago I converted an old site manually... it was tedious and borderline maddening, but I learned a ton about Lumos and saved $42 I guess so there's that haha. Thanks for sharing this!

    • @timothyricks
      @timothyricks  2 місяці тому +1

      Way to look on the bright side! 🙂 Great as a one time learning experience but never having to recreate manually again will be nice.

    • @zeminem35
      @zeminem35 Місяць тому

      Where to the $42 savings come on? On what did you save?

    • @itstoelean
      @itstoelean Місяць тому

      @@zeminem35 In the video, Timothy shares that you can pay for a month of the higher tier account so you can migrate Lumos settings to other sites. This is not available on the account tier I'm on, so instead of paying $42 I did it all manually! It was a lot of work... next time I'm paying for the upgrade lol

  • @Deniz-jn1lv
    @Deniz-jn1lv 2 місяці тому

    Hey, that's awesome! Quick question: Is there any way to control a background video with a press-and-hold action? Essentially, pressing and holding would play the video, and releasing would pause it. I trust your expertise.

    • @timothyricks
      @timothyricks  2 місяці тому

      Yes, it's possible! We would need to use a Webflow Background Video or a Custom Element with a tag of video. There would need to be a section with the class of "video-section". Inside would be the video and also a button with the class of "video-button". Then we would add this script on the Before body tag.
      $(".video-section").each(function () {
      let button = $(this).find(".video-button");
      let video = $(this).find("video");
      video.get(0).pause();
      button.on("mousedown touchstart", function () {
      video.get(0).play();
      });
      button.on("mouseup touchend", function () {
      video.get(0).pause();
      });
      });

    • @DenizKurt-rz3fp
      @DenizKurt-rz3fp 2 місяці тому

      @@timothyricks you are absolutely amazing!

  • @EthanSuero
    @EthanSuero Місяць тому +1

    Worth adding the "Section / Starter" to the page wrap before making the component so you also transfer that component over. I personally use that to start every section on my projects.

    • @timothyricks
      @timothyricks  Місяць тому

      Thank you, Ethan! That component should already be under the "Global" category on the styleguide page. Was it not showing up for you?

    • @EthanSuero
      @EthanSuero Місяць тому

      @@timothyricks Nope, the last project I installed Lumos was missing the Section / Starter, so for all news I always drop the section into the page wrapper before I turn it into a component and share the library. No biggie, perhaps I have an older styleguide? It's the Lumos v2.

    • @timothyricks
      @timothyricks  Місяць тому

      Oh, I see! It might be an older version of V2

  • @bjarnithors
    @bjarnithors 2 місяці тому

    Thank you so much this is really helpful. Now I can both upgrade old sketches and get a better understanding of how the system works.

  • @rafairibarrem
    @rafairibarrem 2 місяці тому +1

    I can already foresee a cool lumos lib coming up!

    • @timothyricks
      @timothyricks  2 місяці тому +2

      I wish they had an option to choose which components to import. That way we could build a massive library of 100 different navbars or footers, and you just choose the one you want. But for now, the best solution is allowing users to copy in unlinked components that have to be manually linked like this…
      www.timothyricks.com/components

  • @rhia.1234
    @rhia.1234 2 місяці тому

    Hey Timothy, been fiddling with the Lumos system for a minute now but noticed something quite frustrating that I can't figure out how to fix. Is there a way to override the data-theme so that Lumos does not insert a background color onto a section? For example, I'm trying to add a 100vw/vh hero section to my page with its own styled background, but because I'm using Lumos, it's forcing the themed background on top of whatever I've done in this section. Not sure how to fix it and I've spent a good hour and a half messing with this, so any pointers would be extremely helpful. Thanks for any help, and thanks for sharing such an awesome system with us to begin with!

    • @timothyricks
      @timothyricks  2 місяці тому

      Hi Rhia, I'm sorry you're running into this issue! If we select the element that has a data-theme attribute and change its background color by using the style panel, the style panel will override the color coming from the data attribute. It's best practice to include the data-theme attribute on the outermost parent, and apply any custom backgrounds to that element or its children.

    • @rhia.1234
      @rhia.1234 2 місяці тому +1

      @@timothyricks Awesome, I'll try that! Thank you so much for your help. :)

  • @divonci-world
    @divonci-world 2 місяці тому +2

    Christ is Lord, I was just thinking of this a week ago. Its like we all think it and Timothy articulates our thoughts through youtube videos hahahaha!!!

  • @xantisant
    @xantisant 2 місяці тому +5

    🙀I swear not half an hour ago i was thinking "but how would i get this into an old project?" 🔮

    • @timothyricks
      @timothyricks  2 місяці тому +1

      Oh, awesome! 😂 Perfect timing. This used to be sooo tedious before libraries released yesterday

  • @iliutacristian8322
    @iliutacristian8322 2 місяці тому

    Do you have a video for people just starting with Lumos, maybe one where you build a landing page from scratch explaining everything you do with Lumos, I have been using Finsweet's Framework for some time now because that's what clients request, but after watching some of your videos I feel like your framework could be much better? Thanks and great work T.

    • @timothyricks
      @timothyricks  2 місяці тому +1

      Hi, I have a Lumos Course made up of short videos that explain each part of Lumos in full detail. The course ends with building a landing page from scratch using Lumos, but it’s helpful to watch the main lessons first to understand the core concepts. Class naming in Lumos is designed to improve site speed, decrease build time, and make the site more maintainable.
      ua-cam.com/play/PLoXSZEwtbyStInsfWsEO5ouJ7HTfMMLeA.html&si=MgnJkCqlVVS4UmBv

    • @iliutacristian8322
      @iliutacristian8322 2 місяці тому

      @@timothyricks Ty

  • @fpv_jesus
    @fpv_jesus 2 місяці тому

    You sir, are a decedent of the gods.

  • @njanadesign
    @njanadesign 2 місяці тому

    that was my request! thank you so much dude

    • @timothyricks
      @timothyricks  2 місяці тому

      Oh, awesome! Thank you for bringing it up!

  • @TerpkeZ
    @TerpkeZ 2 місяці тому +1

    Can you make a video on boosting page speed in Webflow ? (If you already did I apologize lol)

    • @timothyricks
      @timothyricks  2 місяці тому

      Thank you for the great suggestion! I don’t have one of those yet. Personally, I find using webp images, using GSAP instead of Webflow Interactions, and using utility classes for nearly everything helps a lot

    • @TerpkeZ
      @TerpkeZ 2 місяці тому

      @@timothyricks oh wow I didn’t know that, so GSAP is less code heavy than Webflow interactions ??

    • @TerpkeZ
      @TerpkeZ 2 місяці тому

      @@timothyricks and what are utility classes ?

    • @timothyricks
      @timothyricks  2 місяці тому

      If we create an interaction that’s only used on one page of our site, Webflow still adds the code of that interaction to every page. Since JavaScript is the second biggest offender of page speed, this can really impact multi-page sites. With GSAP, we can include the code for each interaction only the pages it’s needed. Or even better, we can store it with the related section component so if the client removes that section from one page or adds it to another, the JavaScript is stored inside the section.

    • @timothyricks
      @timothyricks  2 місяці тому

      Utility classes are classes that aren’t related to single section but instead can be used anywhere throughout the site. These are things like grid-column-3 or text-style-h2. If we create a class and apply styles to it, Webflow includes those styles on every page of the site even if it’s only being used on one page. So using reusable utility classes for common styles like flexbox or grid can remove a huge amount of unnecessary code from our site. ua-cam.com/video/_H7VoBSpsgs/v-deo.htmlsi=g6gFg6JbqVH6puGM

  • @yash7630
    @yash7630 2 місяці тому +1

    That's awesome

  • @DANNFIGDESIGNS
    @DANNFIGDESIGNS 2 місяці тому +1

    🔥🔥👩‍🚒🔥🔥