GitHub for Designers

GitHub is for designers too. Push your projects forward by starting feature-centric discussions on GitHub. This webcast talk covers the maybe-not-so-obvious ways Git & GitHub can improve your design workflow.

Transcript

1. Hello, Internet.
   

   View Slide

2. @nrrrdcore
   

   View Slide

3. I’m a designer.
   

   View Slide

4. UI
   UX
   CSS
   HTML
   VISUAL
   

   View Slide

5. Mostly, I make stuff.
   

   View Slide

6. View Slide

7. Build soware
   beer, together.
   

   View Slide

8. Developers are more open, contribute code
   and discuss about bettering each other.
   While Designers seem secretive, ego-filled
   and seeking pointless exclusivity.
   

   View Slide

9. Developers are more open, contribute code
   and discuss about bettering each other.
   While Designers seem secretive, ego-filled
   and seeking pointless exclusivity.
   

   View Slide

10. “At the end of the
    day, we’re all making
    soware.”
    @kneath
    

    View Slide

11. Build soware
    beer, together.
    

    View Slide

12. View Slide

13. 162 Hubbers
    

    View Slide

14. View Slide

15. View Slide

16. We meet somewhere
    in the middle.
    

    View Slide

17. But we all work
    differently, locally.
    

    View Slide

18. View Slide

19. WMCs
    

    View Slide

20. “A website’s design
    should start where
    it’s going to live.”
    @owltastic
    

    View Slide

21. I design in
    HTML & CSS.
    

    View Slide

22. So I’m prey lucky.
    

    View Slide

23. How do we get our work up on GitHub?
    

    View Slide

24. How do we get our work up on GitHub?
    

    View Slide

25. Meet git!
    

    View Slide

26. git push
    

    View Slide

27. git pull
    

    View Slide

28. Version control is an
    awesome design
    tool.
    

    View Slide

29. designers
    update assets with
    git & GitHub.
    

    View Slide

30. But but but...
    

    View Slide

31. The command line is
    tricky!
    

    View Slide

32. View Slide

33. View Slide

34. View Slide

35. View Slide

36. View Slide

37. $ git commit
    $ git pull
    $ git push
    

    View Slide

38. Commit data is
    prey rad.
    

    View Slide

39. Commit history =
    Design history
    

    View Slide

40. Every commit is a
    documented design
    change.
    

    View Slide

41. Every commit is a
    documented design
    decision.
    

    View Slide

42. GitHub gives you a
    way to browse your
    commit history.
    

    View Slide

43. GitHub gives you an
    interface to browse
    your commit history.
    

    View Slide

44. View Slide

45. What’s in a commit?
    

    View Slide

46. Or rather, what can we do with commits?
    

    View Slide

47. Image Diffing!
    

    View Slide

48. View Slide

49. View Slide

50. View Slide

51. View Slide

52. Where are we
    commiing to?
    

    View Slide

53. Feature Branches!
    

    View Slide

54. Master Branch
    

    View Slide

55. Master Branch
    -always clean
    -always ready to deploy
    

    View Slide

56. Master Branch
    Feature Branch
    

    View Slide

57. $ git checkout -b iss53
    git-scm.org
    

    View Slide

58. Master Branch
    Feature Branches
    

    View Slide

59. Master Branch
    Feature Branch
    

    View Slide

60. Master Branch
    Feature Branch
    

    View Slide

61. Pull Requests!
    

    View Slide

62. Master Branch
    Feature Branch
    

    View Slide

63. Master Branch
    Feature Branch
    Commit
    Commit Commit
    

    View Slide

64. View Slide

65. View Slide

66. Discussions happen
    on GitHub.
    

    View Slide

67. View Slide

68. Markdown!
    

    View Slide

69. .md
    

    View Slide

70. View Slide

71. View Slide

72. Design Reviews
    happen on GitHub.
    

    View Slide

73. @github/design
    

    View Slide

74. Future proof.
    

    View Slide

75. View Slide