~/talk

Style Documentation for the Resource-Limited

Talkat RailsConf 2016 · 2016-05-04..05-06· [component-design, ruby-on-rails]
github:bhaibel
slides:none on file

Argues a concrete, incremental method that avoids stop-the-world rewrites: a three-step cycle to identify, codify, document UI components, refactor into Rails helpers or component builders, use SCSS class-extends to consolidate classes, and test output with Nokogiri. Recommends living docs generated with Hologram + KSS and embedding examples so the style guide auto-updates from real code. Claims this is practical for resource-limited teams and notes ActBlue raised $1.1 billion total and about $0.1 billion in the last month or two.

AI-written summary · about

  1. 0:00Start
  2. 3:14you have an accidental styleguide
  3. 5:42look and feel of individual widgets
  4. 14:31step 1: identify
  5. 25:41step 3: document
  6. 29:56document helpers, not just markup
  7. 35:30questions?
~/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.