Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/ It seems that not a week goes by without a shiny new framework of some type — be it CSS or JS. But no matter how awesome they are, each have shortcomings and idiosyncrasies that invariably make you ask, 'Why?' Now imagine someone gave you the ability to start from scratch to create your own framework. No strings. No preconceptions — well, except that it has to be enterprise scale, platform agnostic, and work in a whole host of disparate situations. In this session, Stephanie will talk about some of the challenges, hurdles, tradeoffs, and unique decisions Salesforce UX made on the way to building an enterprise framework.

1. Designing an Enterprise
CSS Framework is hard
​Stephanie Rewis
​Salesforce UX
​

2. Stephanie Rewis
@stefsull
Lead Developer, Design Systems, Salesforce UX

3. 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.

4. Salesforce1

6. ​How do I get my app
to look like this?

7. ​Can I use the CSS in my app?

9. We'd like our prototypers to iterate
more rapidly.

10. We learned our style guide
was too static.

11. Lightning Design System
The next generation of living style guides

12. Lightning
Experience

13. Design System Components
CSS Framework + UI Library

14. Objects/Components
Lightweight
Modular
Reusable
Utilities
Non-semantic
Single Purpose
Dependencies
Tokens

15. Objects/Components
Lightweight
Modular
Reusable
Dependencies
Tokens
Mixins
Functions

16. clarity
Eliminate ambiguity. Enable people to see,
understand, and act with confidence.

17. Clarity and understandability
in class names

18. BEM Naming
Block
Element
Modifier

19. Let's build a house!
.house { block or component name }
.house__door { element or component part }
.house--red { modifier or component variation }
.house__door--white { variation of a component part }

20. We love documentation!

23. efficiency
Streamline and optimize workflows. Intelligently
anticipate needs to help people work better, smarter,
and faster.

24. Design audit and inventory of all
components in designer's comps

25. We broke the components down to
their smallest patterns and objects.

28. Enterprise applications
have some unique traits.

29. Enterprise applications demand
content and data-rich interfaces.
They lack vertical rhythm.

30. Heading levels may vary and our
components should be agnostic.

31. Lists are used for their semantics.

32. You can opt back in to the default
element style using utility classes
or a single wrapper.
<h2 class="slds-text-heading--medium slds-m-right--small">
Medium heading with a small margin on the right.
</h2>

35. Accessibility for all people and
devices is very important.

36. We baked accessibility in:
Semantics matter
ARIA roles
REM unit sizing
We’ve documented what needs to happen when JS is added

37. consistency
Create familiarity and strengthen intuition by
applying the same solution to the same problem.

38. Design Tokens
The basic atoms of the Design System

39. Types of Design Tokens
• Fonts
• Font Sizes
• Font Weights
• Line Heights
• Background Colors
• Text Colors
• Border Colors
• Shadows
• Spacing
• Sizing
• Animation Durations
• Media Queries
• Z-indexes

41. Using Sass and tokens (variables),
you can brand your app.
.slds-lookup__menu {
position: absolute;
width: 100%;
margin-top: $spacing-xx-small;
border: $border-width-thin solid $color-border;
border-radius: $border-radius-medium;
padding: $spacing-xx-small 0;
background: $color-background-alt;
z-index: $z-index-dropdown;
}

43. We play well with others.
.button
.slds-button

44. What is scoping anyway?
<div class="slds">
<!-- Your components here -->
</div>

45. How does scoping help?
<div class="slds">
<!-- Your components here -->
</div>
ul li { margin-left: 20px; }
.slds li { margin-left: 0; }

46. beauty
Demonstrate respect for people’s time and attention
through thoughtful and elegant craftsmanship.

47. SVG icons for beauty at every size

48. Components should render
beautifully at any width.

51. "I’ve been working on a mobile app that has a Salesforce1 look
and feel for the past several weeks. I've been struggling to get the
styling just right so I decided to scratch it and try out the
framework.
I started this at 11am this morning and by the end of the day, I
almost have a complete application that took me previously over
2 weeks to complete."
- Matt M.
Sr. Software Engineer

52. Resources

53. Get the Design System
https://www.lightningdesignsystem.com/resources/downloads
https://github.com/salesforce-ux/design-system/

54. Flexbox Resources
A Complete Guide to Flexbox — CSS Tricks
https://css-tricks.com/snippets/css/a-guide-to-flexbox
Known Bugs and Workarounds for Flexbox — Phil Walton
https://github.com/philipwalton/flexbugs

55. https://developer.salesforce.com/trailhead/module/lightning_design_system

56. Thank you