Not sure if this is a bug or if I misconfigured something here. I noticed while playing with various typography settings that the node title always is displayed in "Myriad Pro...." and not in font family chosen by me.
Same problem with the menu items and block titles. A quick, amateurishly glance over AM style CSS shows that those font families are set there and I guess the Fusion settings cannot override them. Testing with Slate went well so I guess this is a specific problem with AM3.
I attached a pic to demonstrate the problem with AM3.
Quick question aside: I think it could be valuable to use different font settings for content versus things like menu items. Might this be feature request worth filing?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | AM3 Typography.png | 60.97 KB | dddave |
| #2 | Slate allows to change all fonts.png | 31.51 KB | dddave |
Comments
Comment #1
jeremycaldwell commentedChanging the body font won't change the font-family of all the elements on the site, it just sets a default base font-family. So if something isn't specified, like the h1.title, the it uses the default font-family set on the body. Otherwise it uses whatever font-family is directly applied to it as it's more specific than "body". So you will have to change those manually in your CSS to get everything changed out as needed.
Comment #2
dddave commentedSo let me change this issue to a feature request.
Attached is a pic of a node with Slate showing that all text-areas (including heading and menus) changed the font family. My guess is that this is the intended behavior and that at the current state this feature is only half implemented in AM3. I think it would be a good thing to "complete" this feature. Of course changing this manually in the code is not too difficult but I think this feature is meant as a helper for non-code people. Showing them a changed body yet not a changed heading might be a little bit cruel.
This is a pretty cool feature btw.
Obviously my attachment in the OP was "lost" so I attached it again.
Comment #3
dddave commentedHey, this is working now. Thanks!