~/talk

A real-life journey into the opinionated world of 'utility-first' CSS

Talkat Laracon AU 2018 · 2018-10-18..10-19· [css, frontend-architecture]

Argues that switching to utility-first CSS stops most custom stylesheet churn and speeds work dramatically, showing a real refactor from a messy BEM codebase to tachyons and a small flexbox-grid where roughly fifty custom modifiers disappear, the site rebuilds in ten days while camping, CSS drops from ~275KB to less than half, and a new blog ships with no custom CSS, using simple utilities like mt0 to solve recurring layout tweaks.

AI-written summary · about

  1. 0:00Start
  2. 1:46Separation of CONCERNS
  3. 7:06CSS gets hard to UPDATE
  4. 9:18The best way to maintain CSS is to stop writing CSS.
  5. 13:10"Un-semantic" classes are breaking the web.
  6. 13:21Confusion between semantic HTML and semantic classes.
  7. 15:29You stop writing CSS!
  8. 16:18Ridiculously fast WORKFLOW No, seriously!
  9. 19:27What about specificity? Design restrictions?
  10. 21:48CHRISTMAS BREAK
  11. 25:06Stage 1: Tachyons as SUGAR on top.
  12. 27:29UTILITY. LAST versus UTILITY FIRST
  13. 31:08Copy & paste mess
~/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.