ACSS 101.03: Fluid Responsive, Scale-Based Typography

Поделиться
HTML-код
  • Опубликовано: 6 янв 2025

Комментарии • 73

  • @tir7898
    @tir7898 8 месяцев назад +16

    you said you planned on doing one of these per week, and we get 3 the first week? legend. keep it up brother, mega helpful vids!

  •  8 месяцев назад +6

    A new episode of ACSS101 every day. Who needs Netflix anymore? Thank you for this great tool and the entertaining videos!

    • @vaughanprint
      @vaughanprint 8 месяцев назад

      Yes, but now I don't have any time to watch my Netflix stuff what with all the new faces I am seeing on Bricks related RUclips channels. It's ok though, none of them look like Ripley!

  • @stphnmwlkr
    @stphnmwlkr 8 месяцев назад +2

    I knew how this system worked, but being able to see it and dial it in is such a huge improvement. I see beta 2 on your screen... coming soon I hope.

  • @Luca-ui3rn
    @Luca-ui3rn 8 месяцев назад +2

    I have finally understood the type scaling function. Thank you, Kevin!

  • @JacobBall75
    @JacobBall75 8 месяцев назад

    The last section about mapping the variables without using utility classes is super helpful. There’s always something in these lessons to take away, even if you think you know what it’s about!

  • @dahunsi
    @dahunsi 8 месяцев назад

    Love the flexibility of the text properties through tokens. Simply fantastic. Like I said, ACSS is the gift that keeps giving.

  • @lencarter3095
    @lencarter3095 8 месяцев назад

    Thank you for the in-depth explanations - the insights into what ACSS is actually doing helps clarify so much.

  • @LupusDesign
    @LupusDesign 8 месяцев назад

    Love the explanation of tokens. Another example of a golden nugget, Kevin.

  • @bluetheredpanda
    @bluetheredpanda 8 месяцев назад

    omg is it Christmas season already? 😂
    Seriously though, this rocks. I hope this makes the inner workings clearer for everyone.
    And the behaviour where you can just set the override for one “end” and have the plugin work out the rest… *chef kiss* right there.

  • @abdulwaheedorg
    @abdulwaheedorg 8 месяцев назад

    Kevin! You're doing great!
    Thanks for making videos so quickly.

  • @koperkuba
    @koperkuba 8 месяцев назад +3

    The man! The legend! :)

  • @jcdeaton42
    @jcdeaton42 8 месяцев назад

    Awesome series so far. I’m excited about the new 3.0 workflow!

  • @fatcatdesign
    @fatcatdesign 2 месяца назад +1

    Help this lost person find her way...
    At 2:13, you rec setting root font size to 100% (for newbies)
    However, in your YT vid for Setting up a Bricks Blueprint Site,
    ruclips.net/video/hbwO0J9OPZs/видео.htmlfeature=shared
    At around 44:46 you reference "leaving the root font size at 62.5%
    If I'm following PB101, and then ACSS101, which is the best practice to follow for both?

  • @davidwalls2304
    @davidwalls2304 8 месяцев назад

    The last section was another light bulb moment - who knew ACSS could do that, then again, why should I be surprised. ACSS does so much for the developer.

  • @KshitijShah89
    @KshitijShah89 8 месяцев назад

    Third one already! Holy cow. Love it and learning somethinig new everytime.

  • @eucalyptech
    @eucalyptech 7 месяцев назад

    Very powerful, thank you Kevin !

  • @GeneralEnthusiast
    @GeneralEnthusiast 8 месяцев назад

    At 21:31 in the video, you say, "Everything in this list has a variable attached to it.", but it's not obvious what the variable names are. Why not have an icon next to each input field so we can easily copy the variable names?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад +1

      The variable names exactly match the label text. We will likely add the variables to the right click menus at some point. I’m also adding a recipe to make it even easier to apply the variables in a split second. We have to make sure the dashboard doesn’t get cluttered with icons.

  • @geckografix
    @geckografix 8 месяцев назад

    Brilliant, thank you, a big stumbling block averted

  • @membershipmovement
    @membershipmovement 7 месяцев назад

    Well shucks!!! You answered every objection I had thought of with this!!
    Guess its time to pony up some $$$
    😁

  • @Headlikeanorange84
    @Headlikeanorange84 8 месяцев назад

    And the lessons keep on coming! Tyvm!

  • @wpdv
    @wpdv 3 месяца назад

    What is the process for using ACSS in Breakdance when entering var(--h1) * 1.5 ? After hitting enter, the var is not auto changed to a cal, and there are no changes made. Also, when I right click I do not get the ACSS popup window like you show in this video. What am I missing? Thanks

    • @AutomaticCSS
      @AutomaticCSS  3 месяца назад

      Variable expansion doesn’t work in breakdance yet. You probably need to write the Calc manually.

  • @tjveach
    @tjveach 8 месяцев назад

    Amazing job in explaining, very very helpful

  • @markdreaneen9651
    @markdreaneen9651 8 месяцев назад

    Love the lessons!

  • @johnklutz1403
    @johnklutz1403 2 месяца назад

    Hey Kevin, thanks for the video. I'm confused with the root font size. In PB101 there's no discussions of beginners/intermediates should use 100% and pros should use 62.5%. The only thing discussed there is 62.5% makes the math easier since 1rem = 10px in that case. Can you elaborate on this? Wouldn't setting it to 100% for beginners/intermediate just make it more complex since they have to calculate in 16px?

    • @AutomaticCSS
      @AutomaticCSS  2 месяца назад

      It makes the math harder but ACSS has multiple auto rem converter features so you don’t have to do any math.

  • @schatten105
    @schatten105 8 месяцев назад

    I have Advanced Themer for my default stack for bricks-websites. in there I can create custom typographie-classes/variables with a min and max value (maybe I just need an extra realy big size for heros, or something, but also fluid).
    could I do the same the ACSS? creating extra custom font-sizes with your fluid-logic, but not bound to the existing heading-/text-sizes you showed here?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад

      There’s no need. You’re likely just making extra mess.

    • @schatten105
      @schatten105 8 месяцев назад

      @@AutomaticCSS sad to hear tbh

  • @michailgiannopoulos5274
    @michailgiannopoulos5274 8 месяцев назад

    Simply awesome. One question. @20:35 is this a bug of the builder?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад

      I'm not really sure what happened there. I removed a class from an element and the builder didn't seem to respond accordingly.

  • @CodeGreer
    @CodeGreer 6 месяцев назад

    Curious about orphans here. When you cycle through the scales and the H1 breaks into the next line, why does it leave an orphan? I can see on the ACSS panel it says text wrap is pretty. Obviously this is just an example, but I'm building along with the course and my H1 also creates an orphan, but the text does not.

    • @AutomaticCSS
      @AutomaticCSS  6 месяцев назад

      Is this after save and reload page as well?

  • @itspraveensharma
    @itspraveensharma 8 месяцев назад

    Awesome....👏👏

  • @anaselally
    @anaselally 3 месяца назад

    Thank you, Kevin! I have a question: What if I'm working on a multilingual website, and one of the languages is in a different direction, such as Arabic, which is right-to-left (RTL)? Now I have a website with two languages and two different text directions. Your explanations are always enjoyable and effective, and I always learn something new.

    • @AutomaticCSS
      @AutomaticCSS  3 месяца назад

      ACSS is RTL compatible but bricks isn’t, last time I checked.

  • @joshuag4624
    @joshuag4624 7 месяцев назад

    For some reason I don't get the Acss panel in my bricks builder...

    • @AutomaticCSS
      @AutomaticCSS  7 месяцев назад

      Post in the community and we can help you

  • @energeiai99
    @energeiai99 8 месяцев назад

    Another Gem 🎉 salute 🎉

  • @reggiewaysama
    @reggiewaysama 7 месяцев назад

    Hi Kevin, we still need to follow standard Heading sizes right when adjusting the value here?

  • @vaughanprint
    @vaughanprint 8 месяцев назад

    Another great run-through.
    Kevin I have a question I have been meaning to ask for a while… it may be a felony. Say you have a content width of 1280 pix but you want to control the fluid nature just up to 1100px; once the content hits that width the text and headings have reached thier maximum.
    I don't think the sandboxes are available yet. Is this correct?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад

      Is there a reason that would be desirable? I’ll test sandbox today.

    • @vaughanprint
      @vaughanprint 8 месяцев назад

      @@AutomaticCSS Thanks Kevin. Is it desirable? The reason I was thinking is say you are happy with the text being at it's largest, once the content hits a certain content width and after that it's big enough for wider widths? Is that problematic? I'm not sure? Perhaps something to mention not to do if it's a daft idea?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад

      @@vaughanprint It should be at its largest when the content is at its full content width. It stops growing after that anyway, so just make the desired value at full content width?

    • @vaughanprint
      @vaughanprint 8 месяцев назад

      @@AutomaticCSS Will do.

  • @webdesignburgdorf3028
    @webdesignburgdorf3028 9 дней назад

    Why are font sizes set in px rather than rem? Is there a way to switch to rem? I'd rather not have to think in and set things in px anymore.

    • @AutomaticCSS
      @AutomaticCSS  9 дней назад

      Nothing is set in pixels. Pixels is just a reference unit. Everything is converted to rem for you.

    • @webdesignburgdorf3028
      @webdesignburgdorf3028 9 дней назад

      @AutomaticCSS Why px as reference unit? Why can't we have rem as reference unit? I find it confusing to have to enter px when I want rem. Like this, we only see what we get when looking at the final converted code. Why can't we see it right there?
      In Core Framework, e.g., conversion is optional.
      I have set font sizes in rem for a long time, having to set them in px again feels like a step backwards.

    • @webdesignburgdorf3028
      @webdesignburgdorf3028 9 дней назад

      There is this video of our great teacher of CSS: ruclips.net/video/cwfxZRLqyus/видео.html
      ... preaching "DON'T USE PX!", and I 100% agree with everything he says there. Then I look at ACSS and see px everywhere. I hope you understand my confusion.

  • @palagorn
    @palagorn 8 месяцев назад

    Should I use v3.0-beta-1.1 or 2.x for new website ?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад

      Doesn’t really matter. Just keep updating as they get released.

  • @bjoernzosel
    @bjoernzosel 6 месяцев назад

    awesome!!!!

  • @christianmagill3829
    @christianmagill3829 6 месяцев назад

    Why is h4 chosen as the base heading size?

    • @christianmagill3829
      @christianmagill3829 6 месяцев назад

      It's my understanding that by default in HTML H6 tracks with 1rem.

    • @AutomaticCSS
      @AutomaticCSS  6 месяцев назад +1

      If you create 6 text sizes and put them next to the six heading sizes, “M” and H4 are in the same position

  • @jeremiahhundley6629
    @jeremiahhundley6629 2 месяца назад

    LMAO ---> moving to the prerequiste course.

  • @oldfridayboy5597
    @oldfridayboy5597 8 месяцев назад

    Is there no recipe to style a heading exactly like an h1? Adding all these tokens manually seems tedious and unnecessary

  • @NelmediaCa
    @NelmediaCa 8 месяцев назад

    WOW! I'm in the process of removing ACSS classes (still on 2.8) because I use variables and I want the size to be as low as possible...
    Then, I see what you do when you compare using the text size of h1 vs using the h1 class and I'm thinking: "hmm, maybe I should keep it... Is it worth it for the added size (of CSS and maybe JS)?"...
    And then, you show that (at least in v.3) all can be done by referencing the h1 stuff (like h1-text-size and so on)! So, back to saying that I should then disable it...
    But, the question is: Is it worth it? If enabling the typography classes adds, let's say 1kb or less, it's probably not worth it at all...
    And this is the dilema: I have found that ACSS does add to the weight of the page (though for all it's benefit it is absolutely worth it, I'm trying to keep it as small as possible)... Toggling on the Pro mode does leave a lot of stuff on that I'm not sure it's worth it and can also leave some that I use (like link colors) deactivated... I also heard you on a live stream comparing what takes more weight like flex-grids... Is there (or will there be) a video or chart about the weight of each module OR a video about what are the best settings to use of we mainly use variables (but some classes would be good to keep)?
    Great work!

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад

      Nothing has to be removed manually. If you turn off the classes in the dashboard, they're not loaded in the stylesheet.

    • @NelmediaCa
      @NelmediaCa 8 месяцев назад

      @@AutomaticCSS yes, of course! I guess my question wasn't clear... Should we remove everything (i.e. disable) and just go with variables (except maybe a couple of things like grids)? Where is the line between weight and improving development...? Just a matter of preference or there is a "best options"? Again, don't know if Pro mode is what YOU usually use, or you are more aggressive in disabling the options (again, you did mention flex-grids are heavy, but what about the rest)?

    • @AutomaticCSS
      @AutomaticCSS  8 месяцев назад +1

      @@NelmediaCa A lot of it is preference. I turn off more than pro mode does.

  • @markj2297
    @markj2297 8 месяцев назад

    I see you're using beta 2, while we are still on 1.1, that's messed up lol

  • @iamwaqasdotcom
    @iamwaqasdotcom 8 месяцев назад

    Please take some break to let us digest one per week!