-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Icon system using SVG #182
Comments
This comment has been minimized.
This comment has been minimized.
And FWIW, the main goal of those inlined SVGs are to totally replace existing icon-font. I guess inlined SVGs are not the best fit — will need some work, but SVG fragment identifiers are pretty decently supported. Sara Soueidan wrote a post on 24ways and there's a good post and demo on Broken links. Also if progressive enhancement is still a thing for Boosted, SVG sprite could be all black by default and enhanced using CSS masks to color it. This is done in sseeeedd, based on Noah Blon's post on CodePen. |
Another resource: https://ishadeed.com/article/using-svg-icons/ |
Well, that's a pretty good one: Bootstrap released their own icons system : So I guess it's a good inspiration :D And maybe should we have a dedicated Solaris Icons repository, based on this one… |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The Solaris Icon system now has its own REST API endpoint. So I guess we can script something to get those icons, now :) |
If we keep going with icon-font, Bootstrap Icons (PR #515) went with Fantasticon to generate them. |
Interesting issue, which relates to anohter activity GDL is currently working on. We are migrating the solaris icons database into Master Media Digital Assets Management (DAM) platform. This platform is run by brand, and will make diffrent icon file formats more accessible via an API. I suggest we link this project to this DAM activity - let'sdiscuss during an upcoming sprint planning meeting |
There's tons of resources below.
The text was updated successfully, but these errors were encountered: