Why not Vault templates/Styles/libraries in the same way as CC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I was trying to figure out how other companies keep their employees styles/templates ect synced. It seems you either point to a network location or keep the info in the vault working folder and control the locations with the project file.
As I see it the network location approach is better for those that update the styles or templates often and need everyone working from the current version. But gets hairy if you need to work 'offline'
The vault approach is better if you want accountability/history/and backups of the changes as well as the ability to work offline. Plus if I understand correctly if the users are given the ability to define their vault working folder locations you can choose a drive that has ample space.
I was reading the document mentions in this article;
And it looks at the vault approach and how to set up the libraries and I think I like this method, but the biggest headache is the need to force everyone company wide to do a 'Get' when a change is made.
It got me wondering why it couldn't handle these files in the same way Content Center works were it looks directly at the current version in Vault. Now the obvious drawback is the need to be 'Online' again...
Does anyone have a best of both worlds solution to this problem? Ideally it could be carried out with Vault Basic.