search

pulyabacsi / slack-sketch-prototype-kit

Slack Prototype Kit - Sketch Library ( only for Slack Desktop Application )
10 stars 2 forks source link

Version control #1

Open ghs opened 5 years ago

ghs commented 5 years ago

Better if you add the source file to git instead of .sketch so people can contribute and keep track easily of what was changed, etc. If you would like of course :)

Here is some hints https://medium.com/sketch-app-sources/what-does-the-open-sketch-file-format-really-mean-c02a882b6614

pulyabacsi commented 5 years ago

Hi @ghs, Thank you for your feedback and suggestion.
However, I do understand that it would highlight the changes in code format, I hardly see the point to convert my file into this open format. Based on the article you sent it would be useful to see the changes when changes such as anchoring, layer names will happen. (mainly in case of simple changes) I fear that later on when I'm about to add more elements and rearrange the document it will result in a bunch of hardly understandable changes. What do you think? Do you have experience with these kinds of changes?

For the time being, I try to annotate and describe the changes at every commit to keep it clean :)

ghs commented 5 years ago

Hey @pulyabacsi The idea behind having it versioned is to be able to work with many contributors, manage changes easily, etc. You don't have to look at the resulting code from the format because can be really scary :)

Maybe you know it, but in case, check this service https://plantapp.io. I am personally not using it but I do use versioning since the very first day when Sketch opened their format and it have improved our team work a lot.

ghs commented 5 years ago

Here is one good article about few products and their pros and cons :) https://blog.prototypr.io/abstract-vs-kactus-vs-plant-a-guide-of-version-control-solutions-for-sketch-7da0a8ab5105