Switch to Iconify #22

New issue

Open

opened 2023-10-27 15:07:49 +00:00 by thepaperpilot · 0 comments

thepaperpilot commented

2023-10-27 15:07:49 +00:00

Collaborator

Currently we use Material Icons using fontsource. Switching to Iconify would allow devs to use massively more icons from various different sources. We should register the web component so devs don't need to worry about changing any elements to reference additional packs.

My main concern is how this will interact with PWAs. Iconify will cache icons, but I don't think we can pre-emptively load and cache all icons the project will need in advance.

Also I'm not a huge fan of relying on other servers for things to work, so perhaps it'd be nice to host the icons on incremental.social? That's probably overkill and may harm performance though (Iconify has a distributed CDN).

Currently we use Material Icons using fontsource. Switching to [Iconify](https://iconify.design) would allow devs to use massively more icons from various different sources. We should register the [web component](https://iconify.design/docs/icon-components/vue/) so devs don't need to worry about changing any <link> elements to reference additional packs. My main concern is how this will interact with PWAs. Iconify will cache icons, but I don't think we can pre-emptively load and cache all icons the project will need in advance. Also I'm not a huge fan of relying on other servers for things to work, so perhaps it'd be nice to [host](https://iconify.design/docs/api/hosting.html) the icons on incremental.social? That's probably overkill and may harm performance though (Iconify has a distributed CDN).