I was just reading through
this post on
creativebits about version strategies:
I know the Adobe package contains Version Cue, but I never really managed to grasp how it works. Every time I try to learn about it, all I find is marketing mumbo-jumbo instead of a simple tutorial on how to use it, and I get discouraged. If you know a place to learn about it, please share!
Just as I thought, a lot of creative professionals either don't even know that
Version Cue exists or if they do, can't wrap their head around how it works. It's sad because being a software developer myself, no one wants to think that all their efforts into building out a feature are lost to the general audience of that product. What makes Ivan post even more tragic is the fact that his suggested versioning scheme is very similar to what Version Cue does for you behind the scenes.
I've known about Version Cue for quite some time (GoLive Server anyone?) and had the opportunity to start using it last year when my team went from one (lonely ol' me) to now about five people who need to access our graphical assets, designs, and page comps. I quickly realized when the team started to grow that we needed to arrive at a solution that would allow us all to share assets from a central repository and not trip ourselves up from saving over each other's files. We were able to set up the server just fine and with any software, it took us a little bit of time to get comfortable using it but nowadays it works great for us.
I would like to know what all of you think about Version Cue and if a deeper dive into how to use Version Cue and what it's doing would be helpful to anybody. Would it?
Comments [0]