open .sketch, the huge forthcoming changes to design & code collaboration

The creators of Sketch did not make it a big thing when Sketch 43 launched with an open file format. However, it is actually BIG news. The talk will uncover, show and explain why the open file format has so far-reaching implications for engineering and design. It could be the driver for a new workflow in design, implementation and production. After the talk you will also understand why developers should now get excited about Sketch (apart from what they know now). This understanding will help you to make worthwhile contributions to align and improve the product process at your company.

Transcript

1. andree@blended.io twitter & medium @andreehuk open .sketch, the huge forthcoming changes to the design & code collaboration
2. @andreehuk don't repeat yourself (engineering principle)
3. @andreehuk axure can do symbols for years
4. @andreehuk symbols: a common process in (visual) design
5. @andreehuk styling content symbols: a common process in (visual) design
6. @andreehuk open source format
7. @andreehuk UX camp 2016, talk about running smoother projects with VC
8. @andreehuk X (not yet 2016)
9. @andreehuk
10. @andreehuk 43 April 2017
11. @andreehuk 3. unzipped sketch-test copy.zip 1. Copied .sketch file 2. renamed to ZIP
12. @andreehuk json …is an open-standard file format that uses human-readable text to transmit data objects consisting of attribute–value pairs (wikipedia) In a nutshell, it gives us a human-readable collection of data that we can access in a really logical manner. (copter)
13. @andreehuk Manually copied the value for “blue” to “green” and “red” color values for the square
14. @andreehuk 1. After making the changes manually the JSON file, the 3 files and 2 folders, will be zipped again. 2. Then rename to .sketch
15. @andreehuk Result: new color
16. @andreehuk the design repo
17. @andreehuk A typical code repo, local & remote
18. @andreehuk versioning the core .sketch data only
19. @andreehuk code repo design repo
20. @andreehuk the issues with the design repo - Binary files - Sketch wants .sketch - JSON data isn't visual - Most copy in Sketch is not human- readable - Learning a bit of Git
21. @andreehuk from sketch to code
22. @andreehuk .sketch + its data in JSON
23. @andreehuk content & styling (.sketch) styling (web) content (web)
24. @andreehuk (design & code versioning through git)
25. @andreehuk challenges to be solved, e.g. - .sketch files still need to be zipped - Images should not be versioned in repos, Git LFS to the rescue - Convert components to SASS/CSS - Pull in data from remote sources - Artboards are not connected
26. @andreehuk what can we do now, e.g. - Exchange data programmatically - Change data, e.g. colours without Sketch - Build more advanced plugins - Build tools “outside” of Sketch that pull in data from the Sketch file (e.g. Sketch is closed)
27. @andreehuk contact details / linkedin: send an email to get@incuba.de