Going Headless without Losing Your Head
summary
Demonstrates practical headless stacks: WordPress REST API feeding a React/Redux front end called Urban Core / Irving with server-side/isomorphic rendering, used on a state network serving 1 billion page views/month. Highlights a persistent sticky audio player across three live streams implemented with React, and a Fortune.com rebuild solving expensive queries with prefetching and SSR. Includes a mapping app built with WP REST API and vanilla JS, and emphasizes component-returning endpoints that map directly to UI components in production.
AI-written summary · about
chapters (20)
- 0:00Introduction and overview
- 3:07Headless CMS explained
- 7:13Trade-offs and challenges
- 8:19Choosing headless projects
- 10:12Case study: Colorado.gov
- 11:59Introducing Urban Core
- 13:07Urban Core architecture
- 15:14SEO and headless concerns
- 15:38Case study: Fortune.com
- 17:47Case study: West Philly mapping
- 19:10Headless for small projects
- 20:19Team and workflow considerations
- 21:24T-shaped team approach
- 24:56Vertical slice workflow
- 25:40API endpoints and resources
- 28:05Component-based APIs
- 30:31Modular design systems
- 33:10Learning strategies
- 36:09Breaks and productivity
- 38:39Summary and resources
related talks
58mFrontin' like a Back-er
34mFace Your Fear: The Headless WordPress!
22mHeadless architecture and the future of websites
30mMicro Frontends in React — a State of the Art Approach
45mDo Frontend Devs dream of Backend functions?
39mBeyond React
24mIncremental rewrites with React, HTMX, and TanStack Start
47mMeet Your New BFF: Backend to Frontend without the Duct Tape