Is anyone here using a Git-based workflow for collaboration between different type designers?
I remember Peter Biľak telling me about Typotheque using such a workflow one or two years ago, but I was wondering if anybody could share their personal experiences with it.
0
Comments
from my perspective, the key to using git or hg productively in a "design context" is generating (automatically if possible) a visual artifact which is updated from commit to commit since tools like p4diff can handily show you those deltas in a meaningful way. i do that with illustrator files, but it's much more tedious to do for fonts so i usually end up with tenuously descriptive logs like this.
i'm not sure what your workflow is or how you collaborate. I've only needed to share these files with one or two other people and we rarely touch them at the same time, but when we have, it's been nice to have an annotated visual record of where the files have been.
i was sort of hoping that ghostlines would be like a hosted version of phabricator that also rasterized the font's diffs and gave you handy access to an installable font or webfont for any given commit. if it is, i'm sold and it probably will be quite useful in class contexts.
i'd certainly be curious to hear other folks experiences doing collaborative type design using git or hg. there are definitely some cool things you could do to make online font collab and review interesting. sorry if this is super verbose.
There was also a thought of it being used for font distribution to assure customers always receive the latest and greatest version of a font when small updates are performed to the typeface linking git and licensed user accounts.
Hosted web fonts feel more sensible for a more dynamic development/deployment model in my mind.