Pump up the JAM with Gatsby
summary
Gatsby generates static PWAs from any content source using a unified GraphQL layer and a createNode API, builds React pages with server-side rendering, and ships built-in features like image processing that produces traced SVG placeholders and prefetch-on-hover data fetching. Demo shows a fake shop with ~20,000 products where incremental rebuilds take ~30 seconds (full from-scratch build ~3 minutes), final output ~30,000 files / 600 MB. MDX lets editors embed JSX in content and the plugin ecosystem (≈580 plugins, ≈250 sources) glues everything together.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:04A brief history of "CMS"
- 4:39Meet the JAM stack
- 4:56JAM in a nutshell
- 7:14How "static site generators" work
- 10:39How Gatsby works
- 13:28Pages, Layout & Routing
- 19:23query details in page template
- 20:02Frontmatter, JSON & MDX
- 23:14Gatsby Image / Sharp
- 29:12Conclusion
related talks
27mBeyond Static: Dynamic Web Applications with Gatsby
38mLIVE DEMO: Using GatsbyJS to build a decoupled (Drupal) website
50mUsing GatsbyJS to build a decoupled (Drupal) website (Live demo)
10mAn Introduction to Static Web Apps with JAMStack
17mThe Client-Side Revolution, Brought to You by React
19mWhat’s New and What’s Coming?
42mGatsby is Evolving
17mFrom Brittle to Supple: How Gatsby and MDX Made Our Documentation Smoothly