Story Ideas for Coding Club¶
These mini-graphic novel ideas are designed to inspire the adult
readers of this book — teachers, librarians, parents, and engineers
volunteering as mentors — by connecting the practical lessons of
running a coding club to real founders of the coding-club movement
and to grounded, fictional case studies of clubs like the ones
readers will build. Each story can be generated using the
book-media-generator story route, with the suggested panel count or
your own override via --panels N.
Selection Criteria¶
Stories were selected for:
- Relevance — direct connection to a specific chapter or topic in this book's course description
- Practicality — this book teaches adults how to run a club, so most stories are grounded case studies a mentor will recognize, not abstract science history
- Diversity — a mix of real founders of the coding-club movement and fictional composites drawn from common club situations
- Drama — a concrete problem, a decision, and a visible result
Story Ideas¶
1. The Broken Wires on the Motors¶
| Setting | A university-hosted coding club, present day, 100+ students and 40 mentors, USA |
| Theme | Careful observation and small weekly improvements compound into a sustainable club |
| Connection | Kit inventory and tracking, the continuous-improvement log, the "why single-leader clubs fail" thesis in Why This Textbook |
| Panels | 8 — linear discovery (audit → fix → result) |
A new volunteer discovers that every kit's motors have broken wires from careless student handling, forcing kids to hunt for a working one each week. He re-solders, heat-shrinks, and cable-ties the wires, then adds a gold spiral to each axle so students can see the direction of spin — turning a maintenance fix into a teaching tool.
Why this inspires: It shows that a single observant volunteer, not a grand plan, is how great clubs actually get built, one repaired motor at a time.
Already started — see docs/stories/broken-wires/, which has real before/after photos rather than generated panels.
2. Lights, Color, Motion!¶
| Setting | A fictional coding club, present day, USA |
| Theme | Sensory feedback — light, color, and motion — is the single biggest lever for student engagement |
| Connection | LED strips, Moving Rainbow, and the general principle of designing engaging physical-computing labs |
| Panels | 6 — single technique, before/after |
A mentor notices that a quiet temperature-sensor lab barely holds attention, while a box with a moving rainbow LED strip stops every new student in their tracks. She rebuilds the boring labs so each one ends in something that glows, moves, or changes color, and watches engagement climb.
Why this inspires: It gives mentors a concrete, repeatable design rule instead of a vague call to "make it more fun."
Already started — see docs/stories/lights-color-motion/.
3. Challenge Cards Bring Focus¶
| Setting | A fictional coding club where students drift to phones and videos, present day, USA |
| Theme | Visible structure — a tiered set of challenge cards — keeps students on task without a mentor hovering over every seat |
| Connection | Challenge cards, designing and printing challenge cards, curriculum design |
| Panels | 7 — linear discovery (problem → borrowed idea → adoption → payoff) |
A volunteer notices students drifting to social media between coding tasks. After learning that other clubs use color-coded "challenge cards" — green for warm-ups, blue for focus work, black for team challenges — she builds and laminates her own deck, and distraction all but disappears.
Why this inspires: It shows that a simple, visible system can out-perform constant supervision.
Already started — see docs/stories/challenge-cards/.
4. Her Idea¶
| Setting | A September hackathon event, present day, USA |
| Theme | One personally meaningful project — not a lecture — is what turns a reluctant participant into a builder |
| Connection | Elevator pitch, Moving Rainbow kits, holiday-themed projects (Halloween costumes), word-of-mouth recruiting |
| Panels | 8 — mystery + reveal + payoff |
A teenager dragged to a hackathon by her father spends the morning on her phone, until a mentor's glowing LED lanyard gives her an idea: a jellyfish Halloween costume with LED tentacles. She codes for the rest of the day, shows up in November with a finished costume, and brings three friends to the next event.
Why this inspires: It proves that recruiting is rarely about convincing — it's about finding the one idea a specific kid actually wants to build.
Already started — see docs/stories/her-idea/.
5. The Empty Chair¶
| Setting | A fictional coding club's first oversubscribed session, present day, USA |
| Theme | A hard mentor-to-student ratio is a safety and quality decision, not a bureaucratic limit |
| Connection | Mentors, Students, and the 3:1 Ratio; Adding Mentors; Adding Students |
| Panels | 7 — linear discovery (chaos → diagnosis → fixed ratio → calm) |
A club leader lets enrollment grow faster than mentor sign-ups, and one Saturday a single mentor is stretched across fifteen frustrated students. After the session she institutes a strict 3:1 ratio enforced at registration, and the next session runs calm and focused.
Why this inspires: It turns an abstract policy number into a felt, visible before-and-after a mentor will remember.
6. The Unfamiliar Face at the Door¶
| Setting | A fictional library coding club, present day, USA |
| Theme | Trust with families is built through a documented volunteer process, not good intentions alone |
| Connection | Coding Club Charter and Values; Background Checks for Volunteers |
| Panels | 7 — linear discovery (gap noticed → policy written → adopted) |
A well-meaning adult shows up ready to mentor with no vetting process in place, and the club leader realizes she has no way to say yes or no with confidence. She writes a simple background-check and onboarding policy into the club charter, and from then on every new mentor — and every parent — knows exactly what to expect.
Why this inspires: It shows that a five-minute policy gap, caught early, prevents a much harder conversation later.
7. The Waiting List¶
| Setting | A fictional coding club opening registration for the first time, present day, USA |
| Theme | Gating student capacity by confirmed mentor count keeps a club's promise to every family who shows up |
| Connection | Using Student Registration Systems; Eventbrite Case Study; Registering Mentors BEFORE Students; Using Waiting Lists |
| Panels | 6 — single technique, before/after |
Three hundred families sign up for twenty seats within a day, and the club leader panics. She rebuilds registration so student capacity unlocks only as mentors confirm, adds a waiting list, and the next term opens without a single overbooked session.
Why this inspires: It replaces registration anxiety with a repeatable, fair system any reader can copy.
8. The Sticky Notes on the Whiteboard¶
| Setting | A fictional coding club's after-session debrief, present day, USA |
| Theme | A short, honest retrospective after every session is what turns experience into institutional memory |
| Connection | Sending Out Post-Event Surveys; Event Debriefing; The Event Retrospective Checklist; Tracking What You Learned |
| Panels | 6 — single technique, before/after |
Mentors used to leave each Saturday exhausted and say nothing out loud, repeating the same mistakes term after term. A new leader starts a five-minute sticky-note debrief after every session, and by spring the wall of notes has quietly rewritten the club's playbook.
Why this inspires: It shows continuous improvement doesn't require software or budget — just five minutes and a whiteboard.
9. The Bus That Never Came¶
| Setting | A fictional coding club partnering with a Title I school, present day, USA |
| Theme | The biggest barrier to access is often invisible to the people already inside the room |
| Connection | Recruiting Minorities and Women; Working with Under Served Communities; Community Support |
| Panels | 9 — mystery + reveal + multi-step fix |
A club proud of its open-enrollment policy can't understand why almost no students from the school across town ever show up — until a mentor learns there is no after-school bus to the venue. The club partners with the community center instead, moving the sessions to where the students already are, and enrollment from that neighborhood triples.
Why this inspires: It reframes "recruiting" as removing a barrier rather than writing a better flyer.
10. The Grant That Almost Wasn't¶
| Setting | A fictional coding club's treasurer's desk, present day, USA |
| Theme | Persistence through paperwork and one rejection is what funds a no-fee club |
| Connection | Establishing a Budget; Why No-Fees for Students; Raising Funds; Writing Grants |
| Panels | 8 — linear discovery (shortfall → first rejected grant → revised proposal → funded) |
A volunteer treasurer watches the kit budget run dry and worries the club will have to start charging fees. Her first grant application is rejected for being too vague; she rewrites it with real attendance numbers and a clear budget table, and the second submission funds a full year of no-fee sessions.
Why this inspires: It normalizes rejection as part of the funding process instead of a sign to give up.
11. The Notebook Dan Left Behind¶
| Setting | A fictional coding club as its founding leader relocates for a new job, present day, USA |
| Theme | A club that survives a change of leadership was never really about one person |
| Connection | The central thesis of the book: clubs that depend on a single leader fail; the capstone Coding Club Startup Playbook |
| Panels | 9 — linear discovery with a payoff at the end |
The founding leader of a thriving club has to step away with two weeks' notice. Because he spent three years writing down the charter, the curriculum, the mentor-training notes, and the retrospective log, a new co-leader picks up the binder and runs the next session without missing a beat.
Why this inspires: It makes the book's core promise visible — sustainable infrastructure, not a single hero, is what keeps a club alive.
12. The Agent That Answered at Midnight¶
| Setting | A fictional coding club leader's kitchen table, present day, USA |
| Theme | AI agents can absorb the repetitive administrative load so mentors spend their time with students, not spreadsheets |
| Connection | AI, Intelligent Textbooks, and Where Coding Clubs Meet; Leveraging AI Agents; Communication AI Agents |
| Panels | 7 — linear discovery (overwhelm → first agent → trust → time given back) |
A club leader answering registration emails at midnight, every night, sets up an AI agent to draft replies, track waiting-list openings, and flag anything that needs a human. She reviews its first week of drafts carefully, then lets it run — and gets her evenings back.
Why this inspires: It shows AI as a way to protect mentor time for kids, not a replacement for the human relationships the club runs on.
13. First Steps Across the Threshold¶
| Setting | A fictional coding club's very first Saturday of the term, present day, USA |
| Theme | The first sixty seconds inside the door decides whether a nervous family comes back |
| Connection | The "Walk In Experience"; What Parents and Students See; Designing a Welcome Statement |
| Panels | 6 — single technique, before/after |
A shy student and her uncertain parent stand at the doorway of a club that has no greeter, no signage, and no clear place to sit — and they nearly leave. The next term, a simple welcome table, a name tag, and a mentor stationed at the door turn that same hesitant walk-in into a returning regular.
Why this inspires: It shows how much a small, deliberate welcome ritual determines who a club actually reaches.
14. The Wall of Badges¶
| Setting | A fictional coding club's display wall, present day, USA |
| Theme | Small, visible recognitions rewire a struggling student's sense of "I can't do this" into "I'm a coder" |
| Connection | Motivating Students; Challenge Cards; Badges and Stickers |
| Panels | 6 — single technique, before/after |
A student who has quietly told herself for months that coding "isn't for people like her" earns her first badge for finishing a small project. She starts choosing harder challenge cards on purpose, and by the end of term her badge row covers half the display wall.
Why this inspires: It makes the abstract idea of "growth mindset" concrete enough for a mentor to actually build.
15. Turtles All the Way Down¶
| Subject | Seymour Papert (1928–2016), South Africa / United States |
| Theme | Children learn best by building and debugging their own creations, not by being told the answer |
| Connection | Promoting Computational Thinking; Turtle Graphics; the workshop, hands-on-project model every chapter of this book assumes |
| Panels | 12 — full life arc |
A mathematician working with Jean Piaget in Geneva grows convinced that children reason best through their own hands-on constructions. At MIT he co-creates the LOGO programming language and its turtle, spends decades arguing that computers should let kids build ideas rather than drill facts, and coins the word "constructionism" — the philosophy every coding club, knowingly or not, is built on.
Why this inspires: It gives club mentors the intellectual backbone for why hands-on projects work better than lectures.
16. Imagine, Create, Share, Reflect¶
| Subject | Mitchel Resnick (b. 1956), United States |
| Theme | Learning works best when it looks like kindergarten — imagine, create, play, share, reflect, repeat |
| Connection | Scratch; Designing Your Curriculum; Learning Maps |
| Panels | 9 — thematic arc, contemporary and ongoing |
A researcher at MIT's Media Lab, frustrated that most educational software just drills students on facts, leads the team that builds Scratch — a free, colorful programming language that lets kids of any age make games, animations, and stories. Millions of children worldwide now take their first coding steps inside a tool built on his "Lifelong Kindergarten" philosophy.
Why this inspires: It shows a direct line from a single research group's philosophy to the exact tool many club leaders will hand a first-time student.
17. The Garage Where Everyone Was Welcome¶
| Setting | Gordon French's garage and the SLAC auditorium, Menlo Park, California, 1975–1986 |
| Theme | A loosely organized, all-volunteer club of hobbyists sharing knowledge for free can change the world |
| Connection | What Is a Coding Club; Background on Coding Clubs; Community Support |
| Panels | 8 — founding story, linear |
Thirty computer hobbyists cram into a Menlo Park garage in 1975 to trade parts, swap code, and teach each other on borrowed machines. Nobody in that first meeting of the Homebrew Computer Club is paid to be there — and within a few years its members, including a teenage Steve Wozniak, help spark the personal computer revolution.
Why this inspires: It is the direct historical ancestor of every free, volunteer-run coding club in this book — proof the model works at the largest possible scale.
18. Each One Teach One¶
| Subject | James Whelton and Bill Liao, Cork, Ireland (CoderDojo founded 2011) |
| Theme | A teenager's raw enthusiasm plus an experienced mentor's structure can seed a worldwide movement of free coding clubs |
| Connection | Establishing a New Coding Club; Coding Club Charter and Values; the entire premise of this book |
| Panels | 8 — founding story, linear |
A teenage hacker known locally for jailbreaking iPods starts informally teaching other kids to code after school. When he meets entrepreneur Bill Liao, the two turn that informal habit into "CoderDojo" — free, volunteer-run coding clubs with a simple motto, "each one teach one" — that spreads from one Cork classroom to thousands of Dojos across the world.
Why this inspires: It is, quite literally, the origin story of the "coding club" this whole book teaches readers to run.
19. Code for Every Kid¶
| Subject | Reshma Saujani (b. 1975), United States |
| Theme | Noticing who is missing from the room is the first step toward fixing it |
| Connection | Recruiting Minorities and Women; Working with Under Served Communities |
| Panels | 8 — founding story, contemporary |
While visiting schools during a political campaign, a lawyer notices computer science classrooms full of boys and almost no girls. She leaves politics to found Girls Who Code, building after-school and summer clubs designed specifically to close that gap — and to prove to a generation of girls that coding is theirs too.
Why this inspires: It turns a single observed absence in a classroom into a concrete, replicable club model.
20. The Clubhouse With No Locked Doors¶
| Setting | The Computer Museum, Boston, and the MIT Media Lab, founded 1993, United States |
| Theme | Giving underserved youth open access to real creative tools, not just supervised drills, builds confidence and community |
| Connection | Building Mentor-Student Relationships That Last; Working with Under Served Communities |
| Panels | 8 — founding story, linear |
Researchers at MIT's Media Lab partner with Boston's Computer Museum to open an after-school space where teens from the neighborhood can freely use real design and programming tools with adult mentors instead of a fixed curriculum. The model — youth-driven projects, caring mentors, an open drop-in schedule — becomes the Computer Clubhouse Network, eventually reaching underserved communities on six continents.
Why this inspires: It shows that trusting young people with real tools, not simplified toys, is itself a form of respect that keeps them coming back.
21. AI Racing League¶
| Setting | A fictional suburban home and public high school, present day, USA |
| Theme | Coding clubs often find their best resource in a local retired engineer looking for purpose |
| Connection | Leveraging retired-engineer mentors; Recruiting Minorities and Women; Working with Under Served Communities; Writing Grants; a club's growth into a multi-school league |
| Panels | 13 — linear discovery with a real struggle arc (retirement → restlessness → challenge → discovery → skeptical pitch → demo → grant → weak sign-up → dead batteries → buggy software → race day → spread → payoff) |
Charlie, a gray-haired, Hawaiian-shirted retired engineer, drives his wife Joan crazy puttering around a house with nothing left to fix until she tells him to "get a hobby." A midnight video about "Donkey Car" — a Raspberry Pi and camera mounted on a 1/16-scale RC car, trained with machine learning to drive itself — sends him to a skeptical principal at his local high school with a pitch built around reaching underserved youth and girls. A working demo wins her over, a $2,000 grant buys a GPU and three car kits, and the club he starts takes over the school gym for races (first to finish training and complete ten laps wins) before spreading to other schools entirely.
Why this inspires: It shows mentors that the resource they need most may already be retired and two blocks away, just waiting to be asked.
Already started — see docs/stories/ai-racing-league/.
How to Generate a Story¶
To turn any of these ideas into a full graphic novel with generated images, use:
book-media-generator (story route): {Story Title} --panels {N}
Provide the subject's name (and optionally --panels N to override
the suggested count) and the skill will handle the rest — writing
the narrative, creating image prompts, and optionally generating all
panel images via multiple text-to-image APIs (Google Gemini, OpenAI
gpt-image-1, or others). Current cost for high-quality images with
accurate text placement is approximately $0.039 per image, so
$0.039 × (N + 1) per story — about $0.27 for 6 panels, $0.51 for 12
panels.
Ideas 1–4 already have a docs/stories/<dir>/ directory started;
finishing them means writing the full index.md narrative and
generating the remaining panel images, not creating a new directory.