~/talk

Custom CSS is the Path to Inconsistent UI

Talkat React Boston 2018 · on Saturday, 2018-09-29· [css, component-design, accessibility]
slides:none on file

Claim: stop writing custom CSS at the app level and replace it with design tokens and a small set of primitive components for typography whitespace and layout. Evidence: a codebase shows ~20 different buttons from ad hoc CSS. Tools and examples: Box Flex Grid components with responsive props and spacing scale, styled-components (also JSS emotion or CSS modules), a small utility called react-stylist. Outcome: fewer accidental variants, easier reviews, built-in accessibility and consistent spacing and font sizes across the app.

AI-written summary · about

  1. 0:00Start
  2. 0:09Custom CSS is the path to inconsistent UI
  3. 0:32What's the issue?
  4. 2:44CSS is too powerful
  5. 3:25How can we fix that?
  6. 4:35Not all token combinations are good
  7. 5:34Stop writing CSS!
  8. 5:51Primitive components
  9. 7:15Find minimal number of styles to cover most of the use cases of your app or site
  10. 9:11Make impossible states impossible
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.