π§βπ» Day 03: Zoom Facilitation Guide
π― Purpose
Support the VibeCoding + AI Video hybrid session when teaching fully online via Zoom. This guide ensures students can collaborate effectively even if they have no coding background.
π§© 1οΈβ£ Pre-Class Setup
π» Tools
- Zoom with Breakout Rooms enabled.
- p5.js Web Editor β editor.p5js.org (no installs needed).
- Prepare 3β4 starter sketches with tweakable parameters (color, motion, density, etc.) and share the links in advance.
- Set up a shared Google Drive folder or Padlet for teams to upload screenshots or short loops.
π§ Roles Overview
Send these before class:
| Role | Description |
|---|---|
| π Tuner | Edits numbers or color values in code. |
| π¨ Vibe Director | Describes aesthetic or emotional changes verbally. |
| π§ Observer / Recorder | Takes notes, screenshots, or logs parameter changes. |
π§± 2οΈβ£ Sorting Students into Teams
β‘ Quick Skill Survey (5 min)
Ask in chat or poll:
βWho feels comfortable changing small numbers or colors in code?β
- Raise hand β Tuners.
- Others β Vibe Directors or Observers.
π§ Pairing
- Goal: 2β3 students per team β 1 Tuner + 1 Director (+1 Observer optional).
- Assign each team to a Breakout Room (labeled Team 1, Team 2β¦).
-
Share a specific p5.js starter link per room. Example:
Team 1 β https://editor.p5js.org/yourname/sketches/vibe-A Team 2 β https://editor.p5js.org/yourname/sketches/vibe-B
π§ͺ 3οΈβ£ Inside Breakout Rooms (~35 min)
Team workflow:
- Vibe Director: Suggests changes (e.g. βmake it calmer,β βadd chaos,β βfade slowlyβ).
- Tuner: Adjusts small parameters (numbers, colors, speed) accordingly.
- Observer: Records changes and screenshots best frames.
π‘ Encourage them to rename variables to match mood:
let vibe = "calm waves";
let chaos = 0.3;
let colorShift = 0.02;
You (and any assistant) can rotate through rooms to provide help and inspiration.
πΈ 4οΈβ£ Collecting Results (10 min)
- Each team exports 1β2 frames via
File β Save Imageor screen capture. - Upload to the shared Drive/Padlet folder.
- Optionally select 1 image per team to run through Replicate video models for short clips.
πͺ© 5οΈβ£ Main Room Showcase (15β20 min)
- Return all to main room.
- Share screen β cycle through team images or short clips.
-
Facilitate short feedback discussion:
- βWhat visual element most affected the vibe?β
- βDid it move the way you imagined?β
- βWhich aesthetic decisions surprised you?β
Optionally hold a quick poll:
- π« Most Hypnotic Vibe
- β‘ Best Chaos Energy
- πΏ Most Organic Flow
π§° 6οΈβ£ Facilitation Tips
- Encourage experimentation: no need to understand syntax.
- Emphasize iteration and description β prompting, not coding.
- If bandwidth issues occur, only the Tuner shares screen while others direct verbally.
- Keep extra starter links in the chat in case a sketch breaks.
- Record the showcase portion for reflection or documentation.
β Summary Workflow
| Step | Action | Tool |
|---|---|---|
| Skill survey | Identify Tuners & Directors | Zoom poll/chat |
| Form teams | Assign Breakout Rooms | Zoom rooms |
| Create | Edit shared sketches | p5.js editor |
| Collect | Upload screenshots | Drive / Padlet |
| Showcase | Discuss results | Zoom main room |
β¨ Goal
Students experience the joy of live, collaborative βprompting through codeβ, even without coding skills, and see how descriptive language drives computational aesthetics.