ACSS 101.03: Fluid Responsive, Scale-Based Typography

Поділитися
Вставка
  • Опубліковано 1 тра 2024
  • Automatic.css offers a fluid-responsive, scale-based typography system that works out of the box and is easy to customize for any and all design requirements.
    In this video, you'll learn:
    - Overview of heading vs text system
    - How to set root font size
    - How to set base heading and text size
    - How to set type scale
    - How the base size and type scale work together
    - How to use heading and text variables
    - How to calc sizes for granular control
    - How to use heading and text classes
    - How to manually override heading and text sizes
    - How to manipulate typography on-the-fly
    - How classes pass on all styling and not just type size
    - How to use ACSS' scoped typography variables
    Free training on relative units and root font size: • PB101: L05 - Static vs...
    Interested in using Automatic.css on your sites and accessing the private ACSS support and strategy community? Get a license here: automaticcss.com
    Interested in using Frames on your sites and accessing the private Frames support and strategy community? Get a license here: getframes.io
    Want more helpful dev tutorials and agency-related trainings? Check out Kevin's channel: / @gearyco
  • Розваги

КОМЕНТАРІ • 61

  • @tir7898
    @tir7898 2 місяці тому +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!

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

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

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

      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 UA-cam channels. It's ok though, none of them look like Ripley!

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

    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!

  • @stphnmwlkr
    @stphnmwlkr 2 місяці тому +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.

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

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

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

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

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

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

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

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

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

    Brilliant, thank you, a big stumbling block averted

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

    The man! The legend! :)

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

    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.

  • @Luca-ui3rn
    @Luca-ui3rn 2 місяці тому +2

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

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

    Very powerful, thank you Kevin !

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

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

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

    Mind Blown. Right Clicking menu is a very cool thing.

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

    And the lessons keep on coming! Tyvm!

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

    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.

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

    Love the lessons!

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

    Awesome....👏👏

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

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

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

    Another Gem 🎉 salute 🎉

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

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

  • @bjon3048
    @bjon3048 11 днів тому

    awesome!!!!

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

    Amazing job in explaining, very very helpful

  • @CodeGreer
    @CodeGreer 24 дні тому

    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  23 дні тому

      Is this after save and reload page as well?

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

    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  2 місяці тому +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.

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

    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  2 місяці тому

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

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

      @@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  2 місяці тому

      @@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 2 місяці тому

      @@AutomaticCSS Will do.

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

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

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

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

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

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

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

      Post in the community and we can help you

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

    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  2 місяці тому

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

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

      @@AutomaticCSS sad to hear tbh

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

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

  • @christianmagill3829
    @christianmagill3829 5 днів тому

    Why is h4 chosen as the base heading size?

    • @christianmagill3829
      @christianmagill3829 5 днів тому

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

    • @AutomaticCSS
      @AutomaticCSS  4 дні тому +1

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

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

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

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

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

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

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

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

    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  2 місяці тому

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

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

      @@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  2 місяці тому +1

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

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

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

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

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