Tracking original font icon sources in Fluid projects

Hung, Jonathan jhung at
Wed Jan 13 16:02:44 UTC 2016

For the past few years, we have been using IcoMoon to generate custom icon fonts which we use in various Fluid projects. When making our icon fonts, IcoMoon generates a ZIP file which includes:

  *   the font binaries (TTF, WOFF, and EOT font files)
  *   SVG files which were used to make the glyphs in the font
  *   selection.json file which includes metadata used by IcoMoon to make the font.
  *   a demo.html file with CSS

In our repositories, we only track the font binaries - which creates an issue if we ever want to modify the font. In order to modify the font, we will need the SVG files so we can edit the glyph, and the selection.json file.

I’m wondering if we should start tracking the SVG and the selection.json files within a ./font/source/ directory in our projects. This way anyone can add and modify the font set easily. We should also add a README file in that directory explaining its usage as well.

Thoughts? Yays or nays?

- Jon.

Jonathan Hung
Inclusive Designer
Inclusive Design Research Centre
OCAD University<><>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list