What is your workflow, folder structure, setup?
A lot of my design "assets" are web prototypes and HTML/CSS styleguide components. I keep them in a single Design repo in my company's GitHub org. Each project has its own directory with either a gruntfile or a Meteor app, depending on the kind of work to be done. I generally start code work by copying one of my grunt/meteor boilerplates.
We keep logos, images, etc in Dropbox or Google Drive.
Thanks! This is what I was looking for.
I think a lot of people are considering GitHub as a service to store and manage the revisions in PSD files due to their recent PSD preview feature.
It's a cool feature, but it's a bit misleading imo. Git is not particularly well suited for binary files, it stores diffs for every revision in your working copy, and you download them all when you clone a repository. This means that your repo will grow dramatically in disk usage, and cloning a repo becomes painfully slow.
Contrast that with LayerVault and similars, where you get only the latest revision in your hard drive.
Github doesn't recommend storing PSD assets into git. They recommend using a 3rd party syncing/storage service like LayerVault or Dropbox: https://help.github.com/articles/what-is-my-disk-quota#large-media-files
They then recommend storing the actual asset files (exported PNG/JPG/etc.) files in git for the devs.
Apparently this is what the guys at Github actually do.
GitHub just added PSD support. https://github.com/blog/1845-psd-viewing-diffing
They added PSD support to preview but still have a 100MB file limit. They still recommend to keep your PSDs outside of Github. This support is probably aimed at smaller, more specific, PSD asset files.
Git ( or GitHub by extension) isn't very good for binary files. I find Dropbox works far better as a versioning and backup method. If you want all the sweet diff , comment and other collaborative functions you probably want LayerVault.
Absolutely. But use bitbucket.org (more storage, more private repos). Also using a repo removes you from a machine dependency. You can jump on any box and in seconds have all your files. Worry free.
Stop using PS, file size is too large and pixels are so last season. Go Vector. Sketch, iDraw, AI ...
I use a structure of source, and production files, then version folders inside each.
The bigger question is who's going to start using it now that it diffs PSDs (and hopefully more soon?). How does that change the number of designers who know how to use git or are willing to learn?
Sort of, in the sense that the assets for our site end up in the github repo. But I doubt that's what you mean.
Do you mean managing assets before you're at the production level? Like for sharing with coworkers or review?
I'm thinking for either or both of: 1. Keeping track of AI/PSD files 2. Sharing in progress work for review. 3. A place to put the most recent exports of icons, fonts, etc.
1) usually the AI/PSD files aren't really viewed as assets. Assets are the usable pieces that come out of those files.
2) I doubt github is the place for this, unless your entire team is already active there and knows their way around
3) perfect for this, almost exactly what git was made for
I know it's supported, I'm just saying that Github probably isn't the venue for your non-techie CEO, or the biz-dev guy. I think you'd get more mileage out of a tool specifically targeted at non-developers.