GitHub for Designers

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.

Cbfa54275010d81ff786ef9b2a711d38?s=128

Julie Ann Horvath

May 07, 2013
Tweet

Transcript

  1. Hello, Internet.

  2. @nrrrdcore

  3. I’m a designer.

  4. UI UX CSS HTML VISUAL

  5. Mostly, I make stuff.

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

  8. Developers are more open, contribute code and discuss about bettering

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

    each other. While Designers seem secretive, ego-filled and seeking pointless exclusivity.
  10. “At the end of the day, we’re all making soware.”

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

  12. None
  13. 162 Hubbers

  14. None
  15. None
  16. We meet somewhere in the middle.

  17. But we all work differently, locally.

  18. None
  19. WMCs

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

    @owltastic
  21. I design in HTML & CSS.

  22. So I’m prey lucky.

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

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

  25. Meet git!

  26. git push

  27. git pull

  28. Version control is an awesome design tool.

  29. designers update assets with git & GitHub.

  30. But but but...

  31. The command line is tricky!

  32. None
  33. None
  34. None
  35. None
  36. None
  37. $ git commit $ git pull $ git push

  38. Commit data is prey rad.

  39. Commit history = Design history

  40. Every commit is a documented design change.

  41. Every commit is a documented design decision.

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

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

  44. None
  45. What’s in a commit?

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

  47. Image Diffing!

  48. None
  49. None
  50. None
  51. None
  52. Where are we commiing to?

  53. Feature Branches!

  54. Master Branch

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

  56. Master Branch Feature Branch

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

  58. Master Branch Feature Branches

  59. Master Branch Feature Branch

  60. Master Branch Feature Branch

  61. Pull Requests!

  62. Master Branch Feature Branch

  63. Master Branch Feature Branch Commit Commit Commit

  64. None
  65. None
  66. Discussions happen on GitHub.

  67. None
  68. Markdown!

  69. .md

  70. None
  71. None
  72. Design Reviews happen on GitHub.

  73. @github/design

  74. Future proof.

  75. None