Front-End Platform Engineering
summary
A pragmatic path to a front-end platform: build an internal dev portal (Utro-like) with Storybook for component libraries, Backstage for scale, Markprompt + vector DB for searchable docs, and design tokens as CSS variables to auto-sync Figma and code. Consolidation drops vendors from 124 to ~30, design-system adoption reaches 82%, availability improves from ~20 days/year downtime to minutes, and org-wide security fixes roll out in ~3.5 hours. Focus on npm artifacts, CI integration, feature flags, and upgradeability.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker background
- 4:40Defining front-end platform engineering
- 8:37Building a platform from simple components
- 13:13Design tokens and system scalability
- 17:47Platform engineering results and metrics
- 20:37Adoption strategies and team culture
- 21:42Platform monetization and success
related talks
22mSetting up Enterprise Frontend for Success
15mEstablishing Platform Teams to Utilize the Economy of Scale
44m5 Building Blocks for Successful Frontend Platform
25mEnterprise Final Frontier – is it possible to change the corporate ways...
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
41mMicro-frontends: the golden circle
22mSetting up Enterprise Frontend for Success
21mMicro-frontends: 3 years ago