Replies: 1 comment
-
|
@vonovak Do you have any thoughts on this? Fontawesome are releasing v7 soon so it is a good opportunity to do something different. My thinking is something like
Or perhaps we even drop the 7. Fro what I can tell FA don't touch previous versions after a new one is released My rationale is that it cements our package per font even further, and we can remove some of the complexity we have around the current Font Awesome packages with the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have moved to a
package per fontapproach, which raises an interesting question about "multi icon fonts" like Fontawesome 6 and Material Icons.Should Fontawesome 6 be multiple packages?
The current Pro font has 17 fonts. These are comprised of 5 styles with 4 weights each (ignoring brands). The saving grace here is that, given that this is a paid font, it's up to the user to choose which fonts to include in their application.
Material Symbols would have a similar issue with three different font styles.
I lean towards separate packages for each style as this would remove a lot of complexity, especially around the typescript types.
@oblador, do you have a view of the best approach for existing and new fonts?
NOTE: I've created this discussion on the back of #1703
Beta Was this translation helpful? Give feedback.
All reactions