You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have one icon set that is available as a web font. Most other icon sets are moving towards SVG and discouraging the use of their web font. And we have the issue that the current web font build process is broken. But we also have to consider that many projects already use the existing web font.
While we consider what to do with the web font and its build process, we could create a library of icons that are available in SVG format. We would take all of the existing icons and make them available as SVG, and then add new SVG icons to the library.
As a result, this library may contain icons that are not available in version 1.2 of the font.
The upside:
It is easier to add icons to a library of SVG icons, since no build process is required.
We can collaborate with other icon makers and include their SVG icons in our set (assuming compatible license).
People can use individual icons without needed a web font.
There is no need for a CDN, since there is no web font for this icon set.
The downside:
The web font won't include all of the icons in our library, at least right away. And many people use the existing web font.
We would have to make it clear that the SVG library is not the same as version 1.2 of the web font.
If we do create a separate SVG icon library, we would need to come up with a way to distinguish it from the existing web font.
The text was updated successfully, but these errors were encountered:
Currently, we have one icon set that is available as a web font. Most other icon sets are moving towards SVG and discouraging the use of their web font. And we have the issue that the current web font build process is broken. But we also have to consider that many projects already use the existing web font.
While we consider what to do with the web font and its build process, we could create a library of icons that are available in SVG format. We would take all of the existing icons and make them available as SVG, and then add new SVG icons to the library.
As a result, this library may contain icons that are not available in version 1.2 of the font.
The upside:
The downside:
If we do create a separate SVG icon library, we would need to come up with a way to distinguish it from the existing web font.
The text was updated successfully, but these errors were encountered: