Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.We need to rethink fonts, Google Fonts have added "effects" which I would love to take advantage of, however atm Google fonts are kind of broken in the theme, they sort of work but styles and script sets are not working.
Need to rethink how this can be simplified and this might tie in good with the UI Kit variables for fonts as well (just thinking out loud here).
Comments
Comment #1
Jeff Burnz CreditAttribution: Jeff Burnz commentedThis is now fixed and there have been changes to how fonts are setup and applied.
1) Fonts are now "setup" before they can be applied to elements - you can select a websafe font, Google fonts, Typekit fonts or enter a custom stack. Google fonts are simply the URL from the Google Font Wizard, and Typekit you enter the JS script URL. AT will take care of building the link and script elements for importing these external files.
2) Once you have the fonts setup you can then apply them to elements such as the site name, slogan, titles, headings, local tasks etc, as well as entering custom CSS selectors. When using a Google or Typekit font you simply enter the name of the font when applying it. This is because a Google Font Wizard URL can hold many Google fonts, same with Typekit Kits.
Comment #2
Jeff Burnz CreditAttribution: Jeff Burnz commentedNote that at this stage @font-your-face support has been removed, I will revisit this later on when we are closer to a Drupal 8 Core release and see where @font-your-face module is at, I always liked supporting that module and giving it as an option, however in our user survey it turned out to be a little used feature, with most users favouring Google Webfonts and custom stacks. Personally I use Google fonts and Typekit quite a lot so I have a leaning towards direct support for Typekit.