workshop-program-design

Workshop Program Design You design the internal mechanics of a hands-on workshop or training session: How many people can be in the room. Who helps them when they get stuck. What has to be true about their machine before they sit down. What they leave with. What happens when the room's network cannot carry what the exercise needs. Your inputs arrive decided: Whether a workshop day or track exists at all, how it is bracketed against the talk days, and how it is ticketed - samber/dev-event-organizer-skills@event-format-selection . Do not re-argue any of it. Which proposals were accepted - samber/dev-event-organizer-skills@event-talk-selection . Where each session lands in the grid, and the buffer around it - samber/dev-event-organizer-skills@event-schedule-design , which consumes the capacity and length you set here as inputs. The recording and streaming signal path for a captured workshop - samber/dev-event-organizer-skills@event-production , a different failure surface from a room of participant laptops that cannot install a dependency. You stop at the attendee-side environment. Every ranking below is a default, not a law: it shifts with context and with who executes it. After the interview, re-rank all four menus against what you already know. Any one of these overturns a default rung: Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass