How should we address content file mappings - deep linking perhaps?

Topics: General
Oct 10, 2013 at 9:12 PM
Edited Oct 11, 2013 at 8:55 AM
As someone who is using content based deployment, I have a bit of a different view. What I'd like to see is that I, as a consumer of a content package, can check those content files into my vcs, maybe diverge from the author's implementation, and if a new version comes along, just update, do a simple diff, resolve any conflicts, be done with it.

As long as the explicit support for putting the version number at the end of the file doesn't interfere with the above, go for it.