Distributed Version Control using Git on server

[stephaniel38832060]

Hi,

I am using CC. I am working with close to 200 artwork files.

Workflow ->Save packaged file containing images, fonts and vector onto a Server. Once the file has been packaged I want to be able to manage versions/revisions by other users. Versions will be managed with Git. Being a packaged file, do the links and font folders automatically update when an older/newer version is opened?

Again, I would like to keep the ai. file name the same within the packaged folder.

1. Is there a better workflow for avoiding confusion between versions short of renaming and repackaging every version "_Rev3"?

2. Does it make sense to zip/compress the entire package after a revision and utilize that as the version?

Any workflow changes/suggestions would be appreciated. Last year I ran into issues with myself making the files, the other office I was collaborating with and then the printer.

Thanks!

[Kevin Stohlmeyer]

If you want total control, you should look at a full fledged DAM instead of Git.

That being said, modified links will be honored and managed by the encompassing AI file if the locations and names do not change. If you revise a supporting file and name it _Rev3 the link will be broken and must be reestablished.

[stephaniel38832060]

Thank you for the response. I think that was the answer I was looking for!