Skip to main content
This topic has been closed for replies.
Correct answer rob day

Hi @Phaidon294857876egp , Also for version control you might look at your Creative Cloud Sync folder which stores incremental saves of your documents. Any file you save into your local user>Creative Cloud Files folder will automatically sync to your cloud account. If you right click the file and choose View On Website there is a Timeline option. In this example I can get past saved versions:

 

 

 

2 replies

rob day
Community Expert
rob dayCommunity ExpertCorrect answer
Community Expert
May 9, 2023

Hi @Phaidon294857876egp , Also for version control you might look at your Creative Cloud Sync folder which stores incremental saves of your documents. Any file you save into your local user>Creative Cloud Files folder will automatically sync to your cloud account. If you right click the file and choose View On Website there is a Timeline option. In this example I can get past saved versions:

 

 

 

Joel Cherney
Community Expert
Community Expert
May 9, 2023

Not really. There's always Git Large File Storage, It'll store text pointers in your git that lead to offsite storage, so it'll let you do file versioning in git if that's your intent. Here's a post I cribbed off of to set it up, some years ago.

 

I have seen version control of text content only with git. Text was stored on Github in Markdown, which was then converted into .icml files via pandoc. Those .icml files can be placed and linked in InDesign. I liked that a lot; the dev people got their granular versioning, but they couldn't mess with the graphical stuff. (That was good because allowing the devs to make decisions about visual stuff like logo placement or complementary color was a massive time-sink. Like, insufferable art school freshmen who were all being paid $300k+/yr to argue about color theory.)  

James Gifford—NitroPress
Legend
May 9, 2023

Allowing anyone in the dev hierarchy to write one word of what are meant to be useful docs is no better.

 

I've spent most of a career trying to insulate and firewall user/support docs from developers and rarely succeeding in most terms. I think there are those in docs who have learned this, and those who haven't... yet.