Unresolved Design Decision: Variable Fonts in Devicon for File Size Reduction
0 reputation · 12 Aug 2020, 08:27 UTC
Background
Devicon is a lightweight icon library that delivers its glyphs exclusively through CSS class names and an SVG sprite sheet. The library contains only static assets—@font‑face declarations and elements—without any runtime JavaScript, which effectively eliminates the typical sources of memory leaks in single‑page applications.
Documented Feature
The official documentation describes two primary consumption patterns: referencing icons via class names such as .devicon-devicon-plain and using elements to pull entries from devicon.svg. Both approaches load the entire font or sprite at page load, and no lazy‑loading mechanism is built into the package.
Unresolved Decision
While the current implementation is stable, the project maintainers have flagged an open design question: should Devicon shift to variable fonts to reduce the overall file size while preserving visual fidelity? This change would alter the asset pipeline and potentially impact cross‑browser rendering.
Questions for Review
Which variable‑font formats (e.g., WOFF2, WOFF) provide the best coverage across modern browsers for a library like Devicon?
What measurable effects on design fidelity and loading performance would result from replacing the static font with a variable‑font implementation?
Which metrics and testing strategies should guide the decision to adopt variable fonts in the next Devicon release?
devicon