Case Study - React Finland
summary
Custom site and mobile app for React Finland (about 300 attendees) use a content-first architecture: content lives in GitHub, a GraphQL layer exposes it, and a custom site generator plus Webpack, React, GraphQL build static pages that work even in old browsers. CI publishes content as NPM versions via semantic-release-like commits, Amplify gives site-per-commit previews and PR deploys, and a Chrome-edit prototype commits edits to GitHub and triggers rebuilds. The workflow reduces coupling and the preview loop proves very useful.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:31What was it like in 1995
- 1:09How did we develop websites
- 1:55The homepage
- 2:57The web ring
- 4:06The web stack
- 4:58The site
- 6:10Architecture
- 7:42Content
- 11:23Site per commit
- 13:27Design
- 17:52Recap
- 19:09Editing content
- 21:13Static sites
- 22:25Charm stack
- 23:35The future
- 25:08Announcement
related talks
26mFrontend At Scale - Experiences Using React In A Large Organization
24mCase Study: Creating a Component Library in React JS
16mEnhancing your Static Sites with React Server Components
43mBuilding a component based library with React
23mReact & the JAMstack
15mBuilding world-class web apps using Frappe and React
28mPresentations with React and GraphQL
41mBuilding a design system with React in 2025, what's new?