Standard workflow in maintaining and creating icon fonts

Hung, Jonathan jhung at
Tue Aug 22 20:07:26 UTC 2017

I think it makes sense that we should have copies of the AI and AIA files attached on the wiki since this is already a common practice where the latest artifact is attached to wiki docs (given that it is a reasonable file size).

Also by having copies on the wiki, it would provide some security against unintended modification, deletion / moving of the linked files in OwnCloud.

However, this will create a maintenance task of making sure the Wiki doc is up to date with any meaningful modifications.

As an aside, currently we don't have a good best practice for dealing with content in OwnCloud that is intended to be more permanent.

To answer your question, shared links from OwnCloud also default to the latest version available.

- Jon.

From: Justin Obara <obara.justin at>
Sent: August 21, 2017 3:18 PM
To: Fluid Work; Guerrero, Eloisa; Hung, Jonathan
Subject: Re: Standard workflow in maintaining and creating icon fonts

In regards to attaching the AI and AIA files, I think you can just link to the resources in their current location. For example add a link from ownCloud.

Jon, if we link from ownCloud, does the link stay up-to-date with the latest, or does it point to a specific version?


On August 21, 2017 at 2:09:04 PM, Hung, Jonathan (jhung at<mailto:jhung at>) wrote:

Hi Eloisa,

Thanks so much for doing this!

I went through the guide and have some comments / thoughts.

We like to share what we've learned with others, so it may be useful to approach the documentation from a couple perspectives:

  1.  someone who isn't too familiar with Illustrator
  2.  someone who isn't very technical (upon mention of "command prompt" and they've already hit the back button on their browser. :) )
  3.  someone who is from outside the IDRC

This means you may have to describe things in greater / simpler detail or link to resources that help. For example you may want to describe how to import an Action into AI, or maybe link to a resource that shows you how to import .AIA files.

For the parts of the documentation where it is Would it be possible to generalize the instructions to have both general and IDRC specific instructions? Perhaps attach the AI and AIA file to the wiki page so those not at the IDRC can use that as an example.

Regarding the grunt-webfont generation, it may be helpful to back up a little and say what the prerequisites are (i.e. Step 1. Install npm<>, etc.).

Also it's not immediately clear how grunt-webfont is installed without the fontforge engine. Their project documentation mentions an `engine` option, but doesn't explicitly give instructions. It may be useful to type out exactly what is required.

As for the rest of the documentation, it would be useful to give pointers to other documentation on how to use icon fonts. i.e. maybe the icon font documentation on Fluid project<> or elsewhere on the Wiki is useful?

Incidentally, the existing icon font documentation on the Fluid Project should get updated / deprecated once this documentation get finalized.

Let me know if you want me to clarify anything.

Thanks Eloisa for going down this rabbit hole! 😊

- Jon.

Jonathan Hung, Inclusive Designer
Email: jhung at<mailto:jhung at>
OCAD University
Inclusive Design Research Centre

From: fluid-work <fluid-work-bounces at<mailto:fluid-work-bounces at>> on behalf of Guerrero, Eloisa <eguerrero at<mailto:eguerrero at>>
Sent: August 15, 2017 12:54:31 PM
To: Fluid Work
Subject: Standard workflow in maintaining and creating icon fonts

Hi everyone,

Here’s the documentation for creating icon fonts… If you have any comments or suggestions, it would be greatly appreciated!


fluid-work mailing list - fluid-work at<mailto:fluid-work at>
To unsubscribe, change settings or access archives,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list