Sass & Style Guides

for Squares Conference 2015

Transcript

1. SASS &
 STYLE GUIDES @JINA // SQUARES 2015
2. @JINA SENIOR PRODUCT DESIGNER
 DESIGN SYSTEMS
3. UX
4. SAFE HARBOR Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
5. SASS & 
 STYLE GUIDES
6. “IT USED TO BE THAT DESIGNERS MADE AN OBJECT AND WALKED AWAY. TODAY THE EMPHASIS MUST SHIFT TO DESIGNING THE ENTIRE LIFE CYCLE.” — PAUL SAFFO
7. STYLE GUIDES ARE ALL THE RAGE …AND THEY HAVE COME A LONG WAY
8. 2004 // PDF STYLE GUIDE
9. PDFS ARE A PAIN TO MAINTAIN
10. 2007–2008 // WORDPRESS STYLE GUIDE
11. HTTP://ALISTAPART.COM/ARTICLE/WRITINGAINTERFACESTYLEGUIDE
12. DESIGN GUIDELINES UI/PATTERN LIBRARY FRONT-END DEVELOPMENT TOOL
13. KEEP DOCUMENTATION CURRENT & USEFUL
14. WORDPRESS WAS ONLY SLIGHTLY EASIER …AND I WAS THE ONLY ONE UPDATING IT
15. 2010–2011 // LIVING STYLE GUIDE WITH SASS
17. LIVING STYLE GUIDE A STYLE GUIDE THAT USES THE SAME CODE AS YOUR APP
18. ZOMG!
19. SASS + STYLE GUIDES = AWESOME!
20. MAINTAINABILITY
21. BLOG.ENGINEYARD.COM/2011/FRONT-END-MAINTAINABILITY-WITH-SASS-AND-STYLE-GUIDES
22. 2012–2013 // LIVING STYLE GUIDE WITH SASS FOR WEB WIKI FOR IOS & ANDROID
23. DO CSS STYLE GUIDE, LATE 2013
24. NAMING CONVENTIONS?
25. CLARITY > BREVITY
26. KEEP PROPERTIES ORGANIZED
27. VENDOR/ DEPENDENCIES/ BASE/ COMPONENTS/ HELPERS/ LAYOUTS/
28. ADD TOOLS FOR RAPID DEVELOPMENT & TESTING
29. STARBUCKS.COM/STATIC/REFERENCE/STYLEGUIDE/LAYOUT_PROMO_E.ASPX
30. STARBUCKS.COM/STATIC/REFERENCE/STYLEGUIDE/LAYOUT_PROMO_E.ASPX
31. STARBUCKS.COM/STATIC/REFERENCE/STYLEGUIDE/LAYOUT_PROMO_E.ASPX
32. STARBUCKS.COM/STATIC/REFERENCE/STYLEGUIDE/LAYOUT_PROMO_E.ASPX
33. STARBUCKS.COM/STATIC/REFERENCE/STYLEGUIDE/LAYOUT_PROMO_E.ASPX
34. STARBUCKS.COM/STATIC/REFERENCE/STYLEGUIDE/LAYOUT_PROMO_E.ASPX
35. A RESPONSIVE SANDBOX DURING DEVELOPMENT
36. DO RESPONSIVE LAYOUT GUIDE, EARLY 2013
37. PRODUCT DESIGN HAS INTERESTING CHALLENGES
38. SUPPORT MULTIPLE PLATFORMS & DEVICES
39. QUALITY, CRAFT, & CONSISTENCY
40. DESIGN FOR SCALE & MAINTAINABILITY
41. DESKTOP/WEB iOS WATCH, PHONES, TABLETS ANDROID WATCH, PHONES, TABLETS WIN8 PHONES, TABLETS
42. UI LIBRARY
43. SMACSS.COM
44. BRADFROSTWEB.COM/BLOG/POST/ATOMIC-WEB-DESIGN
45. ELEMENTS COMPONENTS LAYOUTS
46. TYPES STATES VARIATIONS
47. DEVELOPER.ANDROID.COM/DESIGN/BUILDING-BLOCKS/SEEK-BARS
48. REDLINES
50. VISUAL CHANGES FOR NATIVE MOBILE WERE A NIGHTMARE
51. PSD ⟶ DROPBOX ⟶ WIKI ⟶ ☹
52. 2013 // LIVING STYLE GUIDE WITH SASS + ERB & YAML/JSON
53. SASS-LANG.COM
54. SASS-LANG.COM/STYLEGUIDE
55. SASS-LANG.COM/STYLEGUIDE/RESPONSIVE-TEST
56. GITHUB.COM/MATTKERSLEY/RESPONSIVE-DESIGN-TESTING
57. WE OPEN SOURCED THE SITE. ANYONE CAN CONTRIBUTE
58. WHAT IF A NEW COLOR GETS ADDED? THE STYLE GUIDE NEEDS TO BE UPDATED, TOO
59. CAN THE SASS & STYLE GUIDE SHARE A SINGLE SOURCE?
60. DON’T REPEAT YOURSELF
61. c: - name: hopbush hex: "c69" - name: bouquet hex: "b37399" <% data.color.c.each do |s| %> $<%= s.name %>: #<%= s.hex %>; <% end %> YML SCSS.ERB
62. c: - name: hopbush hex: "c69" - name: bouquet hex: "b37399" - for s in data.color.c %li{class: "s-" + s.name} %code = "$" + s.name %br/ = "#" + s.hex YML HAML
63. SASS COLOR STYLE GUIDE
64. NOW // LIVING DESIGN SYSTEM
65. STYLE GUIDES MUST BE CURRENT AND USEFUL
66. JACOBRASK.GITHUB.IO/STYLEDOCCO
67. SFDC-STYLEGUIDE.HEROKUAPP.COM
68. ENTERPRISE
 PRODUCT DESIGN CAN HAVE BIGGER CHALLENGES
69. MULTIPLE PLATFORMS & DEVICES MANY PRODUCTS & FEATURES TONS OF PARTNERS BUILDING ON PLATFORM INNOVATING WHILE MAINTAINING LEGACY ACCESSIBILITY REQUIREMENTS
70. DOZENS OF SCRUM TEAMS HUNDREDS OF DEVELOPERS SMALL TEAM OF DESIGNERS
71. HOW DO WE COMMUNICATE DESIGN ACROSS A
 LARGE ORGANIZATION?
72. WHERE CAN I FIND THE ICONS? WHERE CAN I FIND THE ICONS? WHAT COLOR IS THE BUTTON BORDER?
73. REDLINES?
75. #FML
76. DESIGN PAGES
77. DESIGN SYSTEMS
78. “A FRACTURED PROCESS MAKES FOR A FRACTURED USER EXPERIENCE.” — NATE FORTIN
79. DUPLICATION
    䡿 INCONSISTENCIES
80. NO MAINTAINABILITY
    䡿 INEFFICIENCY
81. LACK OF CLARITY
    䡿 CONFUSION
82. WHEN STYLE GUIDES AREN’T CURRENT,
    THEY’RE NOT USEFUL
83. DON’T CREATE A ZOMBIE STYLE GUIDE
84. MAKE DOCUMENTATION A REGULAR PART
 OF YOUR WORKFLOW
85. MAKING SOMETHING NEW? DOCUMENT IT
86. REVISING SOMETHING? REFACTOR & DOCUMENT IT
87. APPLICATION AREA COLORS
88. HOW DO WE KEEP COLORS, SPACING,
    & SIZES CONSISTENT?
89. HOW DO WE MAKE FUTURE DESIGN CHANGES FASTER?
90. HOW DO WE KEEP OUR DESIGN SYSTEM AGNOSTIC?
91. SINGLE SOURCE
 OF TRUTH OR… DON’T REPEAT YOURSELF
92. TYPOGRAPHY COLORS & GRADIENTS BORDERS METRICS & SPACING ANIMATIONS & TRANSITIONS
93. Sass/LESS/Stylus Lightning JSON (iPhone) XML (Android) HTML (style guide) {
94. { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } // Body text $color-text: #000; THEO SASS
95. { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } // Body text color-text = #000; THEO STYLUS
96. { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } // Body text @color-text: #000; THEO LESS
97. { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } colorText = rgba(0, 0, 0, 1) THEO IOS
98. { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } <td>colorText</td> <td>#000</td> <td style="color: #000;”> Lorem ipsum dolor sit amet </td> <td>Body text</td> THEO STYLE GUIDE
99. { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } <!-- Body text color --> <aura:var name="colorText" value="#000" /> THEO AURA
101. THEO-GENERATED DESIGN PROPERTIES REFERENCE
102. CSS — HEX IOS — RGBA ANDROID — 8-DIGIT HEX
103. CSS — REM/EM/PX IOS — PT ANDROID — SP/DIP
104. NO MORE
 HARD-CODED VALUES
105. NO MORE PROLIFERATION OF INCONSISTENT STYLES
106. NO MORE HAVING TO CONTACT EVERY DEV TEAM FOR A MINOR COLOR CHANGE
107. ACCESSIBILITY
108. GITHUB.COM/SALESFORCE-UX/THEO
109. ASSETS
110. ICONS STORED IN A REPOSITORY AS SVGS
111. ICONS DISPLAY IN OUR STYLE GUIDE AUTOMATICALLY
112. ASSETS DISPLAYED IN STYLE GUIDE
113. A CHANGE IN ONE PLACE CHANGES EVERYWHERE
114. TRUE CONSISTENCY
115. COLLABORATION BETWEEN UX + ENGINEERING
116. MEDIUM.COM/SALESFORCE-UX/LIVING-DESIGN-SYSTEM-3AB1F2280EF7
117. MEDIUM.COM/SALESFORCE-UX
118. @SALESFORCEUX
119. DRIBBBLE.COM/SALESFORCE
120. DRIBBBLE.COM/TEAMSASSDESIGN
121. @TEAMSASSDESIGN
122. “BE REGULAR AND ORDERLY IN YOUR LIFE SO THAT YOU MAY BE VIOLENT AND ORIGINAL IN YOUR WORK.” — GUSTAVE FLAUBERT
123. SUSY.ODDBIRD.NET
124. SAN FRANCISCO SASS & FRONTEND MEETUP @ the mixin
125. THANK YOU