Save 37% off PRO during our Black Friday Sale! »

Design Tokens in Design Systems

67bb0a8cd6c1993dba0bfe302852f729?s=47 jina
November 15, 2016

Design Tokens in Design Systems

Given at The Mixin

67bb0a8cd6c1993dba0bfe302852f729?s=128

jina

November 15, 2016
Tweet

Transcript

  1. THE MIXIN // SAN FRANCISCO // 15 NOVEMBER 2016 DESIGN

    TOKENS
 IN DESIGN SYSTEMS @JINA // LEAD DESIGNER // SALESFORCE LIGHTNING DESIGN SYSTEM # D ESIG N SYSTEM
  2. @JINA LEAD DESIGNER // SALESFORCE LIGHTNING DESIGN SYSTEM ORGANIZER //

    CLARITY DESIGNER // SASS
  3. None
  4. FORWARD-LOOKING STATEMENTS 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. LIGHTNINGDESIGNSYSTEM.COM

  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 // TECHNOLOGY FORECASTER
  7. DESIGN SYSTEMS RULE EVERYTHING AROUND ME

  8. BLOG.ENGINEYARD.COM/2011/FRONT-END-MAINTAINABILITY-WITH-SASS-AND-STYLE-GUIDES

  9. LIVING STYLE GUIDES FTW

  10. SASS-LANG.COM

  11. SASS-LANG.COM/STYLEGUIDE

  12. COULD THE SASS & STYLE GUIDE SHARE A SINGLE SOURCE?

  13. COLORS.YAML swatches: - name: "hopbush" value: "c69" - name: "bouquet"

    value: "b37399"
  14. _COLORS.SCSS.ERB <% data.colors.swatches.each do |swatch| %> $<%= swatch.name %>: #<%=

    swatch.value %>; <% end %>
  15. STYLE-GUIDE/COLORS.HTML.HAML - for swatch in data.colors.swatches %li{class: "swatch-" + swatch.name}

    %code = "$" + swatch.name = "#" + swatch.value
  16. SASS-LANG.COM/STYLEGUIDE/COLOR

  17. A DESIGN SYSTEM CONTAINS WHATEVER YOUR ORGANIZATION NEEDS TO COMMUNICATE

    
 DESIGN DECISIONS
  18. “…STYLE GUIDES. NOW, IT’S DESIGN SYSTEMS. IS THIS JUST A

    CHANGE IN THE MARKETING? OR ARE THESE THINGS ACTUALLY DIFFERENT FROM ONE ANOTHER?” — JARED SPOOL // FOUNDER // USER INTERFACE ENGINEERING
  19. “A STYLE GUIDE IS AN ARTIFACT
 OF DESIGN PROCESS. A

    DESIGN SYSTEM IS A LIVING, 
 FUNDED PRODUCT WITH A ROADMAP 
 & BACKLOG, SERVING AN ECOSYSTEM.” — NATHAN CURTIS // FOUNDER // EIGHTSHAPES
  20. FORMER SALESFORCE1 STYLE GUIDE

  21. WHY DID SALESFORCE 
 NEED A DESIGN SYSTEM?

  22. SCALING ENTERPRISE 
 DESIGN IS TRICKY!

  23. 17 YEARS OF LEGACY

  24. 20K+ EMPLOYEES

  25. LOTS OF PRODUCTS Sales Cloud SalesforceIQ Salesforce Quote-to-Cash Data.com Financial

    Services Cloud Health Cloud Commerce Cloud Service Cloud Desk.com Analytics Cloud Wave Apps Community Cloud Chatter Marketing Cloud Pardot App Cloud AppExchange Force.com Heroku Enterprise IOT Cloud
  26. CONSIDER THE 
 WHOLE ECOSYSTEM

  27. None
  28. GREAT TEAM COMMUNICATION 
 IS CRITICAL

  29. WHERE CAN I FIND THE ICONS? WHAT COLOR IS THE

    BUTTON BORDER? WHERE CAN I FIND THE ICONS?
  30. None
  31. None
  32. None
  33. 106 UNIQUE TEXT COLORS

  34. 120 UNIQUE BACKGROUND COLORS

  35. 73 UNIQUE FONT SIZES

  36. DESIGN PAGES

  37. “A FRACTURED PROCESS 
 MAKES FOR A FRACTURED 
 USER

    EXPERIENCE.” — NATE FORTIN // VP DESIGN // EVERNOTE
  38. DESIGN SYSTEMS

  39. L IG H T N I N G E X

    P E R I E N C E
  40. LIGHTNING DESIGN SYSTEM Design Guidelines CSS Framework Icons Resources &

    Documentation Design Tokens
  41. “TRUE COLLABORATION ISN’T THROWING DESIGNS OVER THE WALL. IT’S DESIGNERS,

    ENGINEERS, 
 & THE REST OF THE TEAM 
 SHARING THE RESPONSIBILITY
 TO BUILD A QUALITY PRODUCT.” — DIANA MOUNTER // DESIGN SYSTEMS LEAD // GITHUB
  42. EMPOWER DESIGNERS 
 & DEVELOPERS

  43. ACCESSIBILITY

  44. LOCALIZATION

  45. Red = Down RED = DOWN

  46. Red = Up RED = UP

  47. LOTS OF
 PLATFORMS & DEVICES

  48. HOW DO WE SCALE DESIGN ACROSS OUR ECOSYSTEM AND ALL

    ITS PLATFORMS & DEVICES?
  49. HOW DO WE MAKE FUTURE VISUAL DESIGN CHANGES FASTER?

  50. HOW DO WE KEEP OUR DESIGN 
 SYSTEM AGNOSTIC?

  51. SINGLE SOURCE OF TRUTH

  52. CSS Preprocessors introduced Variables in CSS for better consistency, efficiency,

    & maintainability. SASS, LESS, STYLUS, ETC.
  53. None
  54. DESIGN TOKENS

  55. MEDIUM.COM/EIGHTSHAPES-LLC/TOKENS-IN-DESIGN-SYSTEMS-25DD82D58421

  56. “DESIGN TOKENS ARE DESIGN DECISIONS PROPAGATED THROUGH A SYSTEM.” —

    NATHAN CURTIS // FOUNDER // EIGHTSHAPES
  57. TYPES OF DESIGN TOKENS Spacing Sizing Rounded Corners Font Weights

    Font Sizes Line Heights Font Families Border Colors Background Colors Shadows Text Colors Animation Durations Z-Indexes Media Queries …etc.
  58. “DESIGN TOKENS ARE AN ABSTRACTION FOR EVERYTHING IMPACTING THE VISUAL

    DESIGN OF AN APP/PLATFORM” — SÖNKE ROHDE, VP, UX ENGINEERING, SALESFORCE
  59. NO MORE HARD-CODED VALUES

  60. None
  61. THEO Open source tool for generating 
 Design Tokens

  62. JSON { "name": "COLOR_TEXT", "value": "#000", "properties": "color" }

  63. YAML COLOR_TEXT: value: "#000" properties: "color"

  64. DESIGN TOKENS CONVERTED TO Lightning Sass Less Stylus JSON (iOS)

    XML (Android) style guide color swatches
  65. DESIGN TOKENS ENABLE US TO SCALE OUR DESIGN ACROSS ALL

    THE PERMUTATIONS.
  66. THEO CAN EXPORT TO PROPER COLOR FORMATS CSS — HEX,

    RGBA IOS — RGBA ANDROID — 8-DIGIT HEX
  67. THEO CAN EXPORT TO PROPER SIZING UNITS CSS — PX,

    EM, REM IOS — PT ANDROID — SP, DP, DIP
  68. $color-text-button

  69. t(colorTextButton)

  70. INSTEAD OF THIS: .slds-button { color: #0070d2; }

  71. SASS .slds-button { color: $color-text-button; }

  72. LIGHTNING .THIS { color: token(colorTextButton); }

  73. .ASE
 Adobe Photoshop
 Adobe Illustrator
 Adobe InDesign .CLR
 other design

    apps on Mac COLOR SWATCHES
  74. DESIGN TOKENS:
 PROBLEM SOLVED

  75. TESTING & ENFORCEMENT Enforcement of correct token on correct property

    Accessibility suite of tests
  76. FORM FACTOR OVERRIDES Allow us to override tokens on our

    various supported form factors We’re mobile first, so overrides are specific to medium & large form factors (tablets & desktop)
  77. BONUS!!!

  78. None
  79. None
  80. APPLY DESIGN DECISIONS 
 WITH CONFIDENCE

  81. NO PRODUCT TOO LARGE,
 NO PRODUCT TOO SMALL

  82. None
  83. “JUST BECAUSE SOMETHING IS 
 HARD DOESN’T MEAN IT’S NOT

    
 WORTH PURSUING… IT’S OUR JOB TO SOLVE THOSE 
 PROBLEMS. AFTER ALL, WE’RE IN
 THE INTERFACE BUSINESS. — BRAD FROST // WEB DESIGNER // ATOMIC DESIGN AUTHOR
  84. KEEP THE MOMENTUM GOING

  85. A DESIGN SYSTEM IS 
 NOT A SIDE PROJECT

  86. ZOMBIE
 STYLE GUIDES

  87. IT MUST BE LIVING

  88. “BE REGULAR AND ORDERLY IN YOUR LIFE, SO THAT YOU

    MAY BE VIOLENT AND ORIGINAL IN YOUR WORK.” — GUSTAVE FLAUBERT // NOVELIST
  89. STYLEGUIDES.IO

  90. LIGHTNINGDESIGNSYSTEM.COM

  91. LIGHTNINGDESIGNSYSTEM.COM

  92. OPEN SOURCE AT GITHUB.COM/SALESFORCE-UX

  93. DESIGNSYSTEMS.HEROKUAPP.COM

  94. CLARITYCONF.COM

  95. SASSNEWS.COM NEWS

  96. THANKS! @JINA @THEMIXINSF