When Bootstrap Attacks
summary
A migration from multiple Twitter Bootstrap versions into a single Bootstrap 2.1 instance uncovers concrete costs and fixes: three bootstraps across codebases, 200 PHP templates, 350 controllers, 143 JS files, 97 commits and 346 files changed totaling ~4,000 additions and deletions, one postmortem and 2% test coverage. Work uses PHP/MySQL legacy templates, Backbone/Django modern stack, Mocha/Chai/jsdom and Selenium plus Needle for visual diff tests, namespacing and CSS-prefixing to avoid future regressions.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:46A MODERN WEB APP?
- 3:08TOO MANY BOOTSTRAPS
- 5:392 DAYS LATER
- 7:21BRING IN THE RECRUITS!
- 7:38BOOTSTRAPV2ATHON!
- 9:23FINALLY, 1 MONTH LATER...
- 12:49BOOTSTRAP:ITS JS, TOO!
- 15:01BUT JUST ONE ARCHITECTURE!
- 19:20DONT USE CLASS NAMES
- 22:19TEST YOUR FRONTEND
- 24:40DIFF YOUR FRONTEND
related talks
18mBye-Bye Bootstrap Bloat
42mTwitter Bootstrap Unleashed
21mStuff About Cascading Style Sheets
42mStop using Bootstrap please!
01h 02mLooking forward to Bootstrap 4
07mGiving Bootstrap the Boot
29mPreprocessors, Components, and CSS in JS or: How I Learned to Stop Worrying and Love the Website
31mBreaking up with the bundle