# Screenshots Needed for Vibe Coding Tutorial This document tracks all the screenshots needed for the tutorial documentation, organized by document segment (00-09). --- ## 00-why-vibe-coding.md - Gemini Integration **Context:** Explaining how to use Gemini and export to Colab. **Priority:** Medium **Screenshots needed:** - [ ] **Gemini Tools → Canvas** - Screenshot showing how to access the Canvas feature in Gemini - [ ] **"Export to Colab" button** - Screenshot showing the export button in Gemini interface **Location in doc:** Lines 99-112 --- ## 01-variables.md - Colab Interface Basics ⭐ **Context:** First introduction to Colab interface. Students need to understand the basic UI. **Priority:** High **Screenshots needed:** - [ ] **Text cells vs Code cells** - Side-by-side or annotated screenshot showing both cell types - [ ] **Play button location** - Screenshot highlighting the play button next to a code cell - [ ] **Creating cells** - Show the hover state between cells with "add code" / "add text" options - [ ] **Cell output** - Screenshot showing output appearing below a cell after running `print("The Raven")` - [ ] **Gemini button in Colab** - Show where the Gemini assistant button is located in the Colab interface **Location in doc:** - Lines 15-34: Cell types and creation - Lines 60-65: Running cells - Lines 178-186: Gemini button --- ## 02-lists.md **Context:** Focuses on Python concepts, not interface. **Priority:** None **Screenshots needed:** None - content is code-focused, not UI-focused --- ## 03-loops.md **Context:** Focuses on Python concepts, not interface. **Priority:** None **Screenshots needed:** None - content is code-focused, not UI-focused --- ## 04-dictionaries.md **Context:** Focuses on Python concepts, not interface. **Priority:** None **Screenshots needed:** None - content is code-focused, not UI-focused --- ## 05-functions.md **Context:** Focuses on Python concepts, not interface. **Priority:** None **Screenshots needed:** None - content is code-focused, not UI-focused --- ## 06-api-calls.md - API Key Setup ⭐⭐⭐ **Context:** Students need to set up their OpenAI API key in Colab's Secrets feature. This is where most students get stuck. **Priority:** CRITICAL **Screenshots needed:** - [ ] **Key icon in sidebar** - Show where the key/secrets icon is located in Colab's left sidebar - [ ] **"Add new secret" button** - Screenshot of the secrets panel with the "Add new secret" button highlighted - [ ] **Secret name field** - Show where to enter `OPENAI_API_KEY` as the secret name - [ ] **Secret value field** - Show where to paste the API key value (blur/redact the actual key) **Location in doc:** Lines 20-27, in the "Colab Setup: API Keys" section --- ## 07-structured-output.md **Context:** Focuses on Python concepts (Pydantic schemas), not interface. **Priority:** None **Screenshots needed:** None - content is code-focused, not UI-focused --- ## 08-files.md - Google Drive Integration ⭐⭐⭐ **Context:** Students need to mount Google Drive and navigate the file system. This is the second most common pain point. **Priority:** CRITICAL **Screenshots needed:** - [ ] **Mount Drive permission prompt** - Screenshot of the "Connect to Drive" / "Grant permissions" dialog - [ ] **Folder icon in left sidebar** - Show where the folder/files browser icon is located - [ ] **Drive folder navigation** - Screenshot showing the path: `drive` → `My Drive` → tutorial folder - [ ] **Three dots context menu** - Show the menu that appears when clicking the three dots next to a file/folder - [ ] **"Copy path" option** - Highlight the "Copy path" option in the context menu - [ ] **Refresh button** - Show where the refresh button is in the file browser panel **Location in doc:** - Lines 19-32: Mount Drive section - Lines 44-50: Folder navigation - Lines 55-70: Copy paths section --- ## 09-encyclopedia.md - Expected Results **Context:** Helps students know what they should see when everything is working. **Priority:** Medium **Screenshots needed:** - [ ] **Folder structure** - Screenshot showing what the complete folder structure should look like (texts folder, output folder, etc.) **Location in doc:** Lines 23-27 --- ## General/Reference Screenshots (Can be added to any relevant section) **Context:** These help clarify common states and errors throughout the tutorial. **Priority:** Low **Screenshots needed:** - [ ] **Code cell executing** - Screenshot showing the spinning/loading indicator when a cell is running - [ ] **Successful API response** - Screenshot of what a successful OpenAI API call looks like in the output - [ ] **Error message example** - Screenshot of a common error (like missing API key) to help with troubleshooting **Suggested locations:** - Code cell executing: 01-variables.md - Successful API response: 06-api-calls.md - Error message: 06-api-calls.md or 08-files.md --- ## Screenshot Guidelines When taking screenshots: 1. **Consistency**: Use the same Colab theme/appearance for all screenshots 2. **Annotations**: Add arrows, circles, or highlights to draw attention to specific UI elements 3. **Redaction**: Always blur/redact actual API keys and sensitive information 4. **Context**: Include enough surrounding UI so users can orient themselves 5. **Size**: Screenshots should be large enough to read clearly but not overwhelmingly huge 6. **Alt text**: Add descriptive alt text for accessibility --- ## Implementation Notes Screenshots should be added using markdown image syntax: ```markdown ![Alt text describing the screenshot](../images/screenshot-filename.png) ``` Consider creating a dedicated `_content/project-1/images/` folder to store all screenshots. --- ## Summary by Priority **CRITICAL (Must have first):** - 06-api-calls.md: 4 screenshots - 08-files.md: 6 screenshots **HIGH (Should have):** - 01-variables.md: 5 screenshots **MEDIUM (Nice to have):** - 00-why-vibe-coding.md: 2 screenshots - 09-encyclopedia.md: 1 screenshot **LOW (Optional):** - General/reference: 3 screenshots **Total screenshots:** 21 **Estimated time to capture and annotate:** 2-3 hours