Growing Ember One Tomster at a Time
summary
A concrete claim: community building is engineered like software, using tangible tools — a mascot, vocabulary, sites and local meetups — not vague goodwill. Tomster starts as an illustration (Tomster sketch 2012) then becomes a release-cycle and city-marketing tool; documentation functions as public API; redesigns land through many pull requests; local efforts show measurable growth (600 members, 42 talks 11,000 views) and mentorship plus critique (Ryan Florence sparking Glimmer) actually change outcomes.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:23With Associates
- 3:11design and engineering
- 6:10good defaults
- 6:54composing concepts
- 9:002. language
- 9:39stability without stagnation
- 11:25documentation
- 12:093. user interface
- 15:27hackability
- 18:09mentor
- 18:35explorer
- 20:15in conclusion...
