Design is not a bug ticket - All Things Open 2016 Keynote

505 views

Published on

Open source projects are often driven by technical people, leaving design concerns to be addressed long after the first commit. But good design is just as important to a project’s success and adoption as good engineering. Think you can succeed on technical merit alone without investing in design? Think again! Sass was originally by devs for devs, completely blind to a whole swathe of potential users in the design community. It was only by embracing those designers and building with them that Sass was able to really, truly be the best tool for the job—for everyone.

An illustrated Tale of Two Preprocessors: see how designers decided the victor—and became core contributors.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
505
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
20
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Design is not a bug ticket - All Things Open 2016 Keynote

  1. 1. @RachelNaborsRachelNabors.com
  2. 2. @RachelNaborsRachelNabors.com Thanks for the GitHub link… What does it do?
  3. 3. @RachelNaborsRachelNabors.com What just happened?
  4. 4. @RachelNaborsRachelNabors.com
  5. 5. @RachelNaborsRachelNabors.com
  6. 6. @RachelNaborsRachelNabors.com Design is a FeatureDesign is a Feature
  7. 7. @RachelNaborsRachelNabors.com Oh yeah, design. We can do that later. Right now we’re focusing on functionality.
  8. 8. @RachelNaborsRachelNabors.com Everyone knows our project is the best. We don’t NEED a design effort.
  9. 9. @RachelNaborsRachelNabors.com We KNOW we need design help. But how do we get it?
  10. 10. @RachelNaborsRachelNabors.com Pfft. Designers can contribute at OUR level. And, we don’t have time to train them!
  11. 11. A Tale of Two Preprocessors
  12. 12. sass-lang.comcirca2011
  13. 13. lesscss.orgcirca2011
  14. 14. @RachelNaborsRachelNabors.com
  15. 15. I’m sorry, Chris. I can’t draw beards well.
  16. 16. @RachelNaborsRachelNabors.com
  17. 17. @RachelNaborsRachelNabors.com
  18. 18. Onboarding
  19. 19. @RachelNaborsRachelNabors.com
  20. 20. @RachelNaborsRachelNabors.com
  21. 21. @RachelNaborsRachelNabors.com
  22. 22. Value Proposition
  23. 23. @RachelNaborsRachelNabors.com
  24. 24. @RachelNaborsRachelNabors.com
  25. 25. Branding and Style
  26. 26. @RachelNaborsRachelNabors.com
  27. 27. @RachelNaborsRachelNabors.com
  28. 28. @RachelNaborsRachelNabors.com
  29. 29. @RachelNaborsRachelNabors.com
  30. 30. @RachelNaborsRachelNabors.com
  31. 31. Part Deux We can do better.
  32. 32. @RachelNaborsRachelNabors.com
  33. 33. @RachelNaborsRachelNabors.com
  34. 34. @RachelNaborsRachelNabors.com
  35. 35. @RachelNaborsRachelNabors.com
  36. 36. Getting Design
  37. 37. @RachelNaborsRachelNabors.com
  38. 38. I’m sorry. I can’t draw mountains well, either.
  39. 39. @RachelNaborsRachelNabors.com
  40. 40. @RachelNaborsRachelNabors.com
  41. 41. @RachelNaborsRachelNabors.com Design is not a Bug Ticket

×