Sharing is Caring… At Scale!
summary
A concrete account of building a shared front-end library at BuzzFeed: a package-based buzz blocks system published to NPM, local development wired through rig, a visual gallery for fast review, required unit tests and snapshot/visual regression checks, and a Slack channel for usage questions. It runs across ~472 services, produces about 35 reusable components so far, enforces semantic naming and versioning, and shows that the tooling and guardrails make sharing actually maintainable.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:30What is sharing
- 2:44Frontend development at BuzzFeed
- 5:18Google Deploy
- 7:57Copy Paste
- 9:57Componentized
- 10:59Buzz Blocks
- 12:52Ideas
- 13:30Component Definition
- 14:17Template Definition
- 15:13Cache
- 17:51Documentation
- 19:19Local EFI
- 20:12BuzzFeed
- 20:38Version Management
- 21:26NPM
- 21:53Webhook
- 22:40Developer sensitivity
- 23:39Unit tests
- 24:29Slack channel
- 25:16Where is code being used
- 26:18Success of the project
- 27:33Middle Management
- 27:47Jack Reed
- 28:13The Future of Buzz Blocks
- 29:34Your Job as a Developer
- 30:11Thank you
related talks
28mSharing is Caring… At Scale!
32mKickstarting libraries of shared React components for multiple teams
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
43mBuilding a component based library with React
33mKickstarting a library of internal React components for multiple teams
44mCooking up Better Front-end Applications with Inspiration From the Culinary World
21mShared Components Beyond the Design System
46mBuilding Reusable Components ... That Are Actually Reusable