- Last post
- 6 Responses
I need a better way to control versioning for my team, I was going to test drive abstract https://www.goabstract.com/
But before going all in, I wanted to see what others were using to manage multiple projects with multiple version across multiple designers.
Our current folder system on the shared server is not scaling well. Anybody here have process tips they can share?
We put together a pretty decent folder+naming structure, but I mean.. versioning is still just filename-v1 v2 etc inside of the folders. Admittedly, it's not amazing and could likely be better. But I've yet to actually not be able to find the latest versions of something even a year later.
I would be really interesting to see what others are doing!
I use Invision with Sketch which has version control on the preview side.
I started using git to manage all files in a project (including psd's and sketch files) last year when Github added support for large files and it's been great to be able to roll back changes: https://git-lfs.github.com/
...and you can use Source Tree as a gui so you don't have to use the terminal to manage your repository.
Been using Abstract for a few months now - its pretty much Github for sketch. (Branch from master at the beginning of the day and merge back to master at the end.) The project I'm working on has three teams in three continents working on the same files - we couldn't do this without Abstract.
We don't need our server - everything is stored on Abstract.
What type of work