Flexible Design Systems

Slide 1

Slide 1 text

Delivering Flexible   Design Systems

Slide 2

Slide 2 text

WARNING: THIS TALK CONTAINS MOVING & FLASHING IMAGES. IF YOU ARE SENSITIVE TO THESE IN ANY WAY PLEASE BE ADVISED.

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

Who am I? Just

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

SENIOR DIR., UX PLATFORM GoDaddy ON THE INTERNET THEY CALL ME @INDEXZERO BOARD MEMBER, OPENJS FOUNDATION

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

UX Platform? …?

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

cross cutting All of our technology user experience A BIT MORE THAN JUST OUR DESIGN SYSTEM

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

UXCore2 Our design system ABOUT 50 COMPONENTS REACT BASED OVER 100 CONTRIBUTORS STARTED IN LATE 2015 DEPLOYED WORLDWIDE ~40% OF FRONT END ENGINEERS

Slide 13

Slide 13 text

LET’S BREAKDOWN THE PROBLEM

Slide 14

Slide 14 text

Delivering Flexible   Design Systems Design Systems Flexible Delivering

Slide 15

Slide 15 text

Delivering Flexible   Design Systems Design Systems

Slide 16

Slide 16 text

ELEMENTS of a DESIGN SYSTEM

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

‘sub-atomic’ First off the atomic design of COLOR PALETTE, TYPOGRAPHY, SPACING, “VOICE”

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

COMPONENTS ATOMS & MOLECULES OF ATOMIC DESIGN Lots of

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

LIVING DOCUMENTATION all disciplines for ENGINEERS TECHNICAL WRITERS DESIGNERS CONTRIBUTORS

Slide 23

Slide 23 text

CONSIDER EVEN A SIMPLE BUTTON COMPONENT

Slide 24

Slide 24 text

CONSIDER EVEN A SIMPLE BUTTON COMPONENT

Slide 25

Slide 25 text

CONSIDER EVEN A SIMPLE BUTTON COMPONENT

Slide 26

Slide 26 text

‘intuitive familiar’ equals Raskin, ‘94

Slide 27

Slide 27 text

WORKFLOWS

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

governance of system extensibility The

Slide 30

Slide 30 text

Delivering Flexible   Design Systems Design Systems Flexible Delivering

Slide 31

Slide 31 text

Delivering Flexible   Design Systems Flexible

Slide 32

Slide 32 text

RESPONSIVE DESIGN Assuming of course …yeah? Not up for debate, right?

Slide 33

Slide 33 text

CONSIDER A DROPDOWN ON WEB & MOBILE (REACT NATIVE)

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

FEATURES HOW MANY IS “TOO MANY”?

Slide 36

Slide 36 text

STYLES

Slide 37

Slide 37 text

STYLES CSS? INLINE STYLES? DO YOU NEED BOTH?

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

are you one brand? many? or

Slide 44

Slide 44 text

λ-CALCULUS OF COLOR SELECTION

Slide 45

Slide 45 text

λ-CALCULUS OF COLOR SELECTION

Slide 46

Slide 46 text

λ-CALCULUS OF COLOR SELECTION

Slide 47

Slide 47 text

λ-CALCULUS OF COLOR SELECTION WHAT IF A BRAND WANTS TO USE “SECONDARY” FOR “PRIMARY” BUTTON? MORE BUTTON-SPECIFIC VARIABLES FOR REBINDING In λ-calculus this is an “α-conversion”

Slide 48

Slide 48 text

Delivering Flexible   Design Systems Design Systems Flexible Delivering

Slide 49

Slide 49 text

Delivering Flexible   Design Systems Delivering

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

STAGES of DELIVERY

Slide 52

Slide 52 text

DEVELOP & PUBLISH & PROMOTE & MAINTAIN & ROLLOUT

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

DEVELOP WHERE WORKFLOW IS KING

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

EASY Make it contributors for any new

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

ENTRY POINT Treat every a FIRST INTERACTION as though IT COULD BE

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

small module the

Slide 61

Slide 61 text

small module the most easily is understood

Slide 62

Slide 62 text

No content

Slide 63

Slide 63 text

monorepo Using a

Slide 64

Slide 64 text

monorepo Using a YOUR PACKAGES/**/README.MD STILL MATTERS! diligence requires AND –– npm home your-package

Slide 65

Slide 65 text

Use Storybook (cross platform is still a little rough)

Slide 66

Slide 66 text

Use Storybook (cross platform is still a little rough) storybook Just use color me seriously impressed

Slide 67

Slide 67 text

HAVE an EXAMPLE STRUCTURE

Slide 68

Slide 68 text

No content

Slide 69

Slide 69 text

imagine Now 25+ examples

Slide 70

Slide 70 text

No content

Slide 71

Slide 71 text

EXACTLY WHAT’S A BETTER APPROACH?

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

AS SIMPLE possible with as CLEAR REQUIRE / IMPORT USAGE DESIGN DOCUMENTATION PLATFORM SPECIFIC EXAMPLES ZERO CONFIG, SANE DEFAULTS

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

DOCZ is solving SIMILAR CHALLENGES

Slide 77

Slide 77 text

storybook but is DEVELOPMENT-FOCUSED MORE FLEXIBLE …NOT A FULL SOLUTION

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

npm install @exemplar/storybook-react https://github.com/godaddy/exemplar

Slide 80

Slide 80 text

EXEMPLAR evolving to is USE STORYBOOK PRESETS SUPPORT DESIGN DOCS (MDX) API DOCS (REACT-DOCGEN) SUPPORT MULTIPLE TOOLS (DOCZ)

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

PUBLISH WHAT COULD GO WRONG?

Slide 83

Slide 83 text

No content

Slide 84

Slide 84 text

PRODUCTION begins at PUBLISH TIME

Slide 85

Slide 85 text

No content

Slide 86

Slide 86 text

can break publishing NPM INSTALL & UNIT TESTS UPSTREAM BUILD TOOLCHAINS REACT NATIVE APPS MISCONFIGURED CONSUMERS

Slide 87

Slide 87 text

No content

Slide 88

Slide 88 text

No content

Slide 89

Slide 89 text

PROMOTE ... CONTINUOUS DEPLOYMENT AND THE NATURE OF DESIGN SYSTEMS

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

too many unknowns there are simply …WHEN OPERATING AT LARGE ENOUGH SCALE ANYWAY

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

Let’s ROLLOUT TO PRODUCTION!

Slide 94

Slide 94 text

WARNING: CONSUMER BUNDLES SHOULD NOT INCLUDE YOUR DESIGN SYSTEM OR DEPENDENCIES THAT CHANGE INFREQUENTLY PLEASE BE ADVISED.

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

vendor bundle USE A

Slide 97

Slide 97 text

vendor bundle USE A VENDOR.MIN.JS REACT REACT-DOM REACT-INTL DESIGN-SYSTEM.MIN.JS BUTTON DROPDOWN …ETC. APPLICATION.MIN.JS

Slide 98

Slide 98 text

There should only be one true version

Slide 99

Slide 99 text

There should only be one true version design system of your in production

Slide 100

Slide 100 text

Your computer npm publish your design system npm

Slide 101

Slide 101 text

Your computer npm publish your design system all your users any install version they want npm

Slide 102

Slide 102 text

Your computer npm publish your design system all your users any install version they want npm get different versions!

Slide 103

Slide 103 text

consistent delivery ENFORCE or face peril

Slide 104

Slide 104 text

No content

Slide 105

Slide 105 text

centralized deployment benefits of FIX BUGS FASTER ACROSS SITES EASILY REBRAND YOUR SYSTEM ROLLBACK ANY BREAKS QUICKLY BETTER INSIGHTS INTO USAGE

Slide 106

Slide 106 text

…SOUNDS GREAT! BUT HOW DO I DO IT? I’M GLAD YOU ASKED!

Slide 107

Slide 107 text

webpack externals EXPOSE and version them

Slide 108

Slide 108 text

No content

Slide 109

Slide 109 text

webpack externals? WHAT ARE

Slide 110

Slide 110 text

ANY ORDINARY WEBPACK BUNDLE MODULE LOADER – THE “FACTORY”

Slide 111

Slide 111 text

ANY ORDINARY WEBPACK BUNDLE MODULE LOADER – THE “FACTORY” MODULE 0

Slide 112

Slide 112 text

ANY ORDINARY WEBPACK BUNDLE MODULE LOADER – THE “FACTORY” MODULE 0 module.exports = /* module 0’s code */

Slide 113

Slide 113 text

ANY ORDINARY WEBPACK BUNDLE MODULE LOADER – THE “FACTORY” MODULE 0 module.exports = /* module 0’s code */ MODULE 1 module.exports = /* module 1’s code */ MODULE 2 module.exports = /* module 2’s code */ MODULE 3 module.exports = /* module 3’s code */

Slide 114

Slide 114 text

Slide 115

Slide 115 text

No content

Slide 116

Slide 116 text

ANY WEBPACK.CONFIG.JS

Slide 117

Slide 117 text

ANY WEBPACK.CONFIG.JS

Slide 118

Slide 118 text

CONSISTENT asset DISTRIBUTION

Slide 119

Slide 119 text

Your computer npm publish your design system

Slide 120

Slide 120 text

Your computer npm publish your design system all your users

Slide 121

Slide 121 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm

Slide 122

Slide 122 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm get the same version!

Slide 123

Slide 123 text

REMOVING EXTERNALS RENAMING EXTERNALS ENSURING PROPER USAGE UNEXPECTED CONSEQUENCES

Slide 124

Slide 124 text

YOU MUST have a ROLLBACK  PLAN

Slide 125

Slide 125 text

No content

Slide 126

Slide 126 text

warehouse.ai Using npm dist-tag add @your/package@1.2.3 prod makes this trivial ... TRY IT OUT! HTTPS://GITHUB.COM/GODADDY/WAREHOUSE.AI

Slide 127

Slide 127 text

No content

Slide 128

Slide 128 text

MAINTAIN FIXING FIRES BEFORE THEY HAPPEN

Slide 129

Slide 129 text

No content

Slide 130

Slide 130 text

DEVOPS WHEN THINGS DON’T GO AS PLANNED

Slide 131

Slide 131 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm get the same version!

Slide 132

Slide 132 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm UNEXPECTED DOWN-TIME get the same version!

Slide 133

Slide 133 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm requests next will FAIL! UNEXPECTED DOWN-TIME get the same version!

Slide 134

Slide 134 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm requests next will FAIL! UNEXPECTED DOWN-TIME get the same version! AND  THEN EVERY  CONSUMER  IS  DOWN

Slide 135

Slide 135 text

No content

Slide 136

Slide 136 text

single point the FAILURE of

Slide 137

Slide 137 text

No content

Slide 138

Slide 138 text

LET’S TALK about CACHING

Slide 139

Slide 139 text

No content

Slide 140

Slide 140 text

CACHING PERFORMANCE SAVING COPIES ……FOR SPEED

Slide 141

Slide 141 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm

Slide 142

Slide 142 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm +80ms

Slide 143

Slide 143 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm +80ms +80ms for your users

Slide 144

Slide 144 text

Your computer npm publish Warehouse.ai your design system all your users new request versions every Xm +80ms use always cached copy +80ms for your users +0ms for your users

Slide 145

Slide 145 text

No content

Slide 146

Slide 146 text

FAILOVER CACHING SAVING COPIES ……FOR LATER

Slide 147

Slide 147 text

Your computer npm publish Warehouse.ai your design system everyone is still up! new request versions every Xm requests next will FAIL! UNEXPECTED DOWN-TIME AND  THEN EVERY  CONSUMER  IS  DOWN

Slide 148

Slide 148 text

Your computer npm publish Warehouse.ai your design system everyone is still up! new request versions every Xm requests next will FAIL! UNEXPECTED DOWN-TIME the use FAILOVER CACHE

Slide 149

Slide 149 text

No content

Slide 150

Slide 150 text

OUT-OF-BAND-CACHE THIS IS WHY WE CREATED A REUSABLE npm install out-of-band-cache

Slide 151

Slide 151 text

No content

Slide 152

Slide 152 text

No content

Slide 153

Slide 153 text

HYGIENE PAYING TECHNICAL DEBT

Slide 154

Slide 154 text

... YOU CAN’T AVOID IT

Slide 155

Slide 155 text

... YOU CAN’T AVOID IT WARNING: ON A LONG ENOUGH TIMELINE, IF LEFT UNCHECKED ALL SOFTWARE WILL CRUMBLE FROM TECHNICAL DEBT PLEASE BE ADVISED.

Slide 156

Slide 156 text

No content

Slide 157

Slide 157 text

UPGRADING TO NEW VERSIONS: REACT, BABEL, WEBPACK, ETC. REMOVING DEPRECATED APIS E.G. componentWillReceiveProps, etc. USING LATEST APIS – E.G. PORTALS, REACT@16 CONTEXT, etc.

Slide 158

Slide 158 text

IT ADDS UP QUICKLY UPGRADING TO NEW VERSIONS: REACT, BABEL, WEBPACK, ETC. REMOVING DEPRECATED APIS E.G. componentWillReceiveProps, etc. USING LATEST APIS – E.G. PORTALS, REACT@16 CONTEXT, etc.

Slide 159

Slide 159 text

MAY THE SOURCE BE WITH YOU SLIDES WILL BE POSTED ON TWITTER SHORTLY – FOLLOW ME @INDEXZERO THANKS FOR LISTENING!