Building a Community Around Ignite
summary
A CLI and boilerplate called Ignite becomes a production tool rather than a demo: two maintained stacks (Andres with Redux, Bowser with MobX + TypeScript), a plugin architecture and the Gluegun CLI library power extensibility, and community onboarding via Slack grows to 3,200 people. Generation templates reportedly cut off two to four weeks of project startup time. Outcomes include third‑party boilerplates, steady issue reports, hires sourced from the Slack, and shipped apps.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 0:42About Jamon
- 1:41About Infinite Read
- 2:02About Chain React
- 2:51About React Native
- 3:34About the talk
- 3:58What is Ignite
- 5:08Ruby on Rails
- 5:55Ignite CLI
- 6:35Boiler Plates
- 7:41Ecosystem
- 8:21Community
- 8:41Three Phases
- 9:00Build Something Compelling
- 10:08infinitered
- 10:47feeling the joy
- 11:10feedback loops
- 11:37extensible
- 12:37branding marketing
- 12:51evoke a feeling
- 13:37the logo
- 13:53Gator
- 14:38Get people there
- 15:50Invite people
- 16:12Slack
- 16:43Community Care
- 17:46Set Expectations
- 19:14Feed the Community
- 21:55New Features
- 23:39Supporting Community Solutions
- 24:37Chain Reaction
- 25:13Automation
- 26:11Impact
- 26:58Ignite Red Team
- 28:20Meaningful Connections
- 28:42Sajjad
- 29:30Ignite Health
- 29:46Infinite Read
- 31:38Where to go
related talks
04mInterview with Gant Laborde
49mScalable Best Practices for Your Development Team
06mIgnite: A day in the life of an OSS maintainer
01h 06mDay Two (stream crashed)
20mBuild Fullstack 10x Faster with Blitz.js
40mPanel Discussion: Build a Community, Not a Framework
27m(Re)building a Framework: Lessons, Community, and Impostor Syndrome
05mIgnite: Learning to Share