Bye bye, weeds! Digital Gardening with Astro, SolidJS, & MDX
summary
Migrates a four‑page Gatsby site into Astro with MDX and optional SolidJS/React islands, keeping existing components and switching to Astro’s content collections plus Zod schemas for type‑safe front matter. Shows Astro’s image API producing optimized WebP outputs, ditching heavy Gatsby GraphQL and long configs. Notes a surprising 10‑hour Gatsby upgrade attempt, then a successful Astro build that still exposes CSS load‑order hoisting and buggy view‑transitions — components mostly work but a few layout glitches remain.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:38Speaker and passions
- 3:01Design systems & Gatsby setup
- 5:11Digital gardens & MVP mindset
- 7:21Upgrading Gatsby after 3 versions
- 9:11Gatsby upgrade frustrations
- 11:19Why Astro fits digital gardens
- 12:43Astro over alternatives
- 15:33Gatsby vs Astro configs
- 18:26Project differences & layouts
- 19:32Astro content collections & type safety
- 21:47Simpler data queries with Astro
- 23:12Dynamic pages in Astro
- 24:21Astro image optimization
- 26:07Converting React to Astro
- 28:56Astro pitfalls learned
- 30:04Live demo: Gatsby vs Astro
- 32:33Debugging CSS & transitions
- 35:09Closing & Q&A
related talks
32mBye-bye, weeds! Digital Gardening with Astro, SolidJS & MDX
31mBye-bye, weeds! Digital Gardening with Astro, SolidJS, & MDX
26mAll Things Astro
22mBuilding faster content-driven sites
21mAll Things Astro
15mAll Things Astro
21mRevolutionizing Web Development with Astro Build
30mGoing Full-Stack with Astro