four icons, each in 24 hues, generated programmatically.
the only thing changing between icons is the element,
and the only thing changing between hues is the fill: style on that path.
a DRY-er approach might be to create a view that takes icon id and hue as URL parameters
and dynamically puts the right components into the response SVG
i'm not sure what the implications on caching of either approach would be,
and having a bunch of files in a directory is probably less prone to bugs given we're in a hurry to ship this.
(adding new hues/icons later might be easier with a programmatic approach however.)
(I semi-deliberately didn't choose a perceptually uniform colour map,
so there are e.g. more blues and greens than there are oranges)
four icons, each in 24 hues, generated programmatically. the only thing changing between icons is the element,
and the only thing changing between hues is the fill: style on that path.
a DRY-er approach might be to create a view that takes icon id and hue as URL parameters and dynamically puts the right components into the response SVG i'm not sure what the implications on caching of either approach would be, and having a bunch of files in a directory is probably less prone to bugs given we're in a hurry to ship this. (adding new hues/icons later might be easier with a programmatic approach however.)
(I semi-deliberately didn't choose a perceptually uniform colour map, so there are e.g. more blues and greens than there are oranges)