I just discovered that this component does not work for /pub/ (published) pages. The fonts are not loading on these pages resulting in a default Times New Roman alike font.
The published page tries to load the google font through the theme component:
The font file not being loaded on the published page, it doesn’t fall back to the font-family variable `Arial, sans-serif and uses Times New Roman instead.
There may be room for improvement here as long as the published pages can access the modifications required.
That’s awesome, thank you and your team for developing such a convenient feature ^^. I will recommend it to people I know who are using discourse to build user communities.
Quick bug report: I just noticed when I set the font weight then bold text doesn’t show up as bold.
I tested this with the fonts Work Sans and Zilla Slab. I changed the font weight from the default (400) to 300. When I did this bold text did not appear bold. Reset that setting and the bold text reappears.
I set it to 400 and called it a day, but wanted to let you know.
Any way to get into the nitty gritty a little more? The “Headline” font is coming up as 900 weight by default with Headers inside of Topics. Would be great to set the defaults for each of those Markdown objects.
I’ve just merged a refactor of this component that better aligns with Google Font updates — this should fix some issues people were having with different weights not appearing.
Note that the setting formatting changed slightly so that weights can no longer be included in the font name setting like Roboto:300,300i,500, and this would have to be updated to a simple Roboto… but it should migrate automatically on update.
I really love it.