Screenshots Guide
This guide recommends which screenshots to take to document the application visually.
Screenshot Recommendations
1. Home Page
File: screenshot-home-page.png
What to show:
- Full width, desktop resolution (1920x1080)
- “Students: Join a Session” section with code entry box
- “Instructors: Create Session” button/section
- Responsive layout with both sections visible
Instructions:
- Go to
http://localhost:8000or your production URL - Don’t be logged in to anything
- Show full page with both student and instructor sections
- Desktop view
Why: Users need to see entry points
2. Student Interface - Question Submission
File: screenshot-student-view.png
What to show:
- Student session page
- Question submission text box at top
- Empty or with a few example questions
- Mobile-friendly layout
- Submit button and voting interface
Instructions:
- Open student session in desktop browser
- Don’t submit anything yet (show clean state)
- Show the input box for questions
- Show vote buttons next to questions
- Show upvote count
Why: Students need to see how to submit questions
3. Student Interface - Real-time Updates
File: screenshot-student-with-questions.png
What to show:
- Student view with 5-10 questions
- Questions sorted by upvote count (highest first)
- Different vote counts visible
- Some questions with checkmarks (answered)
- Clean, readable layout
Instructions:
- Create a test session
- Submit several test questions with different vote counts
- Mark some as answered
- Screenshot with questions visible
- Desktop view showing multiple questions
Why: Potential users see real-time voting in action
4. Student Mobile View
File: screenshot-student-mobile.png
What to show:
- Same student view but on mobile (iPhone/Android)
- Portrait orientation
- Questions readable and buttons tapable
- Responsive layout
- Question text visible without horizontal scrolling
Instructions:
- Open student session on mobile phone
- Portrait orientation
- Show question list and voting
- At least 3-4 questions visible
- Screenshot from actual device or browser dev tools mobile view
Why: Users need to see mobile experience works
5. Instructor Dashboard - All Questions Tab
File: screenshot-instructor-all-questions.png
What to show:
- Instructor dashboard main view
- Session title and metadata
- All Questions tab (active)
- 5-10 questions with vote counts
- Question numbering (Q1, Q2, etc.)
- Action buttons visible
- Vote count visible
- Toggle voting button
Instructions:
- Login as instructor
- Go to active session
- Make sure “All Questions” tab is selected
- Have at least 5-10 questions in session
- Desktop resolution (1920x1080)
- Show the full dashboard
Why: Instructors need to see their primary interface
6. Instructor Dashboard - Flagged Questions Tab
File: screenshot-instructor-flagged-questions.png
What to show:
- Instructor dashboard
- Flagged for Review tab (active)
- Red badge showing count
- At least one flagged question
- Censored profanity visible (e.g., “What the *** is this?”)
- ⚠️ flag icon visible
- Approve, Reject, and Delete buttons visible
- All buttons operational (not grayed out)
Instructions:
- Login as instructor
- Go to session with flagged questions
- Click “Flagged for Review” tab
- Submit a test question with profanity to create one
- Show the flagged question with buttons
- Don’t click the buttons yet
Why: Instructors need to understand content moderation workflow
7. Instructor Dashboard - Flagged Question Moderation
File: screenshot-instructor-approve-action.png
What to show:
- Flagged question with buttons visible
- Show buttons: “✓ Approve & Show”, “✗ Reject & Hide”, “🗑️ Delete”
- Buttons are clearly clickable (not disabled)
- Censored text visible
- Original profanity shown in hover/tool-tip (if applicable)
Instructions:
- Same setup as screenshot 6
- Hover over or show the approval buttons
- Make buttons visible and readable
- Show the three button options
Why: Instructors need to know their options for moderation
8. QR Code Display
File: screenshot-qr-code.png
What to show:
- QR code modal/window
- Large, scannable QR code
- Session title near QR
- URL visible below QR code
- Modal title or context
Instructions:
- Login as instructor
- Go to session dashboard
- Click “Show QR Code”
- Screenshot the QR code
- Make it large and clear
- Ensure it’s readable
Why: Teachers need to see how to display QR code for students
9. Instructor Presentation Mode / Stats
File: screenshot-stats-view.png
What to show:
- Stats page or presentation mode
- Large, readable text
- Question count
- Upvote count
- Answered count
- Session title
- Suitable for classroom projection
- Clean, minimal design
Instructions:
- Go to instructor dashboard
- Click “Presentation Mode” or “View Stats”
- Screenshot the full screen
- Ensure text is large and readable
- Show it would be visible on projector
Why: Teachers need to see engagement metrics
10. Admin Panel - Dashboard
File: screenshot-admin-dashboard.png
What to show:
- Admin login page success
- Admin dashboard overview
- Navigation menu
- Statistics visible
- API keys section accessible
- Clean, professional layout
Instructions:
- Login to admin panel with credentials
- Go to dashboard
- Screenshot main admin page
- Show navigation options
- Desktop resolution
Why: Administrators need to see management interface
11. Admin Panel - API Key Management
File: screenshot-admin-api-keys.png
What to show:
- API Keys section in admin panel
- List of existing API keys
- Create New API Key button
- Keys listed with names and status (Active/Inactive)
- Actions (delete, deactivate) visible
Instructions:
- In admin panel, go to API Keys
- Show list of existing keys
- Show “Create New API Key” button
- Screenshot the list view
- Don’t show actual key values
Why: Admins need to see key management interface
12. API Key Creation Success
File: screenshot-api-key-created.png
What to show:
- API key successfully generated
- Full API key visible (blurred/redacted for public docs)
- “Copy to Clipboard” button visible
- Warning about saving the key
- Professional confirmation message
Instructions:
- Create a new API key in admin panel
- Screenshot the success screen
- Show the full key (can be fake/redacted)
- Show copy button
- Show one-time warning message
Why: Admins need to see how to provide keys to instructors
13. Browser Console - Profanity Detection
File: screenshot-console-logs.png
What to show:
- Browser dev tools (F12) console tab
- Log messages showing question received
- Filter/censoring messages visible
- Shows
[STUDENT]or[INSTRUCTOR]prefixes - Multiple messages showing real-time activity
Instructions:
- Open browser dev tools (F12)
- Go to Console tab
- Clear any existing logs:
console.clear() - Submit a question as student
- Screenshot showing new log entries
- Show message about filtering if applicable
Why: Developers/admins need to see system is working
14. Session Report Download
File: screenshot-download-report.png
What to show:
- Instructor session view
- “Download Report” button visible
- Format options (CSV/JSON) shown
- After clicking, the report is downloaded
Instructions:
- End a session in instructor view
- Go to “My Sessions”
- Find ended session
- Show “Download Report” option
- Screenshot the download dialog/options
Why: Instructors need to know how to export data
15. Session Join via QR (Mobile)
File: screenshot-mobile-qr-scan.png
What to show:
- Mobile phone camera
- QR code being scanned
- Safari/Chrome notification to open link
- Clear, in-focus QR code
Instructions:
- Have QR code displayed on computer
- Use mobile phone camera to scan
- Screenshot the moment before clicking the notification
- Ensure QR code is in frame
- Show typical mobile QR experience
Why: Students need to understand QR scanning workflow
16. Error States (Optional)
File: screenshot-error-invalid-session.png
What to show:
- Error message when session code is wrong
- User-friendly error text
- Option to try again
- Professional error styling
Instructions:
- Go to session join page
- Enter invalid session code
- Try to join
- Screenshot error message
- Desktop view
Why: Shows error handling is professional
Recommended Resolutions
Desktop Screenshots
- Width: 1920px
- Height: 1080px
- Format: PNG (for quality)
Mobile Screenshots
- iPhone: 390x844 (typical modern phone)
- Android: 360x800
- Format: PNG
QR Code Screenshot
- Size: Actual size from browser (usually 400-600px)
- Format: PNG (best for QR codes)
File Naming Convention
Use this pattern for consistency:
screenshot-<feature>-<view>-<resolution>.png
Examples:
screenshot-student-view-questions-desktop.pngscreenshot-instructor-flagged-mobile.pngscreenshot-admin-api-keys-desktop.png
Organizing Screenshots
Suggested directory structure:
docs/screenshots/
├── student-view/
│ ├── home-page.png
│ ├── question-list.png
│ └── mobile-view.png
├── instructor-view/
│ ├── dashboard-all-questions.png
│ ├── dashboard-flagged-questions.png
│ ├── qr-code.png
│ └── stats-view.png
├── admin-view/
│ ├── dashboard.png
│ ├── api-keys-list.png
│ └── api-key-created.png
└── error-states/
└── invalid-session.png
Tips for Good Screenshots
-
Use real data - Submit actual test questions, don’t fake the UI
-
Consistent styling - Use same browser, resolution, zoom level for all
-
Show context - Include page titles, buttons, and navigation
-
Clean slate - Close other windows/tabs to minimize distractions
-
High contrast - Ensure text is readable in screenshot
-
Test readability - Resize and view at different sizes to verify legibility
-
Consistent timestamp - Take screenshots at similar times for consistent look
-
Professional appearance - Use production domain names, clean test data
-
Include variations - Show both empty states and populated states
-
Mobile first - Prioritize mobile screenshots as mobile is increasingly important
Updating Screenshots
When to retake screenshots:
- Major UI changes
- New features added
- Color scheme changes
- Resolution/responsive design updates
- At least annually (designs may shift)
Accessibility
When creating screenshots:
- Use high contrast (dark text on light background)
- Include alt text descriptions
- Ensure text is at least 12pt in screenshots
- Use clear, readable fonts
- Avoid small icons (make them visible)
Using Screenshots in Documentation
Template for including screenshots:
## Feature Title
Description of the feature.

**Figure 1:** Student interface showing question list with voting
### How to use this feature
1. Step one
2. Step two
3. Step three

**Figure 2:** API Key management in admin dashboard
Always include:
- Image file path
- Descriptive alt text
- Caption with “Figure X:” numbering
- Context explaining what’s shown
Screenshots Referenced in Documentation
This section lists all screenshots mentioned throughout the documentation and where they should appear.
FAQ Screenshots (docs/FAQ.md)
For Quick Start & Getting Started:
- instructor-login-page.png
- Location: FAQ → “Getting Started”
- Shows: API key entry field, login button
- Purpose: Visual reference for where to paste API key
- session-creation-form.png
- Location: FAQ → “Creating a Session”
- Shows: Session title input, password field, create button
- Purpose: Shows session creation interface
- session-created-success.png
- Location: FAQ → “Creating a Session”
- Shows: Confirmation with both student and instructor URLs
- Purpose: What to expect after session creation
For Sharing with Students:
- qr-code-display-modal.png
- Location: FAQ → “Best way to share?”
- Shows: Large, clear QR code with session title above
- Purpose: Shows students what QR code looks like before scanning
- my-sessions-download.png
- Location: FAQ → “Downloading Session Questions”
- Shows: “My Sessions” view with download buttons for each session
- Purpose: Shows where to find download options
For Moderation:
- flagged-questions-tab.png
- Location: FAQ → “Profanity Questions”
- Shows: “Flagged for Review” tab with red badge count showing flagged questions
- Shows: Censored question text (e.g., “What the *** is this?”)
- Shows: Three action buttons (Approve & Show, Reject & Hide, Delete)
- Purpose: Shows the flagged moderation workflow
- moderation-buttons-close-up.png
- Location: FAQ → “Approve/Reject Questions”
- Shows: Close-up of the three action buttons
- Shows: Button states and labels clearly
- Purpose: Makes button options clear and unambiguous
For Answering Questions:
- answer-writing-modal.png
- Location: FAQ → “Writing Detailed Answers”
- Shows: Answer text editor with markdown formatting
- Shows: Live preview pane
- Shows: Publish button
- Purpose: Shows answer composition interface
- question-with-answer.png
- Location: FAQ → “Writing Detailed Answers”
- Shows: Student view of question with published answer below
- Shows: Instructor response clearly visible
- Purpose: Shows what student sees after answer is published
For Dashboard:
- instructor-dashboard-overview.png
- Location: FAQ → “Session Workflow”
- Shows: Full instructor dashboard with:
- Session title and metadata
- “All Questions” tab
- Multiple questions with vote counts
- Question numbering (Q1, Q2, etc.)
- Action buttons (Mark as Answered, Write Answer, etc.)
- Toggle voting button at bottom
- Purpose: Shows primary workspace
- dashboard-with-checkmark.png
- Location: FAQ → “Marking Questions as Answered”
- Shows: Dashboard with some questions marked with checkmark
- Shows: Visual indicator that question is addressed
- Purpose: Shows what answered questions look like
Instructor Guide Screenshots (docs/INSTRUCTOR_GUIDE.md)
Already documented in guide, recommend adding:
- qr-code-presentation-projector.png
- Location: INSTRUCTOR_GUIDE.md → “QR Code Section”
- Shows: QR code as it appears when displayed on projector
- Shows: Session title clearly visible
- Shows: Instructions for students to scan
- Purpose: Instructor preview of what students see
- voting-toggle-example.png
- Location: INSTRUCTOR_GUIDE.md → “Managing Voting”
- Shows: Dashboard with voting ON (questions sorted by votes)
- Shows: Dashboard with voting OFF (same order)
- Purpose: Visual comparison of voting states
- my-sessions-list.png
- Location: INSTRUCTOR_GUIDE.md → “Managing Sessions”
- Shows: “My Sessions” page with multiple sessions
- Shows: Active vs ended session indicators
- Shows: Status badges and timestamps
- Purpose: Shows session management interface
Troubleshooting Screenshots (docs/TROUBLESHOOTING.md)
Consider adding:
- browser-console-errors.png
- Location: TROUBLESHOOTING.md → “WebSocket Failed”
- Shows: F12 Developer Tools → Console tab
- Shows: Example WebSocket error messages
- Shows: Where to look for errors
- Purpose: Helps users diagnose connection issues
- network-tab-websocket.png
- Location: TROUBLESHOOTING.md → “WebSocket Failed”
- Shows: F12 Developer Tools → Network tab
- Shows: WebSocket connection (ws:// or wss://)
- Shows: Connection status (successful or failed)
- Purpose: Shows advanced diagnosis
Directory Structure for Screenshots
Recommended organization:
docs/screenshots/
├── README.md (index of all screenshots)
├── getting-started/
│ ├── instructor-login-page.png
│ ├── session-creation-form.png
│ └── session-created-success.png
├── sharing/
│ ├── qr-code-display-modal.png
│ └── qr-code-presentation-projector.png
├── moderation/
│ ├── flagged-questions-tab.png
│ └── moderation-buttons-close-up.png
├── answering/
│ ├── answer-writing-modal.png
│ └── question-with-answer.png
├── dashboard/
│ ├── instructor-dashboard-overview.png
│ ├── dashboard-with-checkmark.png
│ ├── my-sessions-list.png
│ └── voting-toggle-example.png
└── troubleshooting/
├── browser-console-errors.png
└── network-tab-websocket.png
Screenshot Priority
High Priority (Essential):
- instructor-dashboard-overview.png
- qr-code-display-modal.png
- flagged-questions-tab.png
- session-creation-form.png
Medium Priority (Important):
- my-sessions-list.png
- answer-writing-modal.png
- instructor-login-page.png
- moderation-buttons-close-up.png
Low Priority (Nice to have):
- browser-console-errors.png
- voting-toggle-example.png
- question-with-answer.png
How to Add Screenshots to Documentation
Once screenshots are captured, add them like this:
In Markdown:

**Figure X:** Explain what user should notice in this screenshot
Example:

**Figure 1:** Instructor dashboard showing real-time questions sorted by votes
Linking Screenshots from FAQ
The FAQ.md file includes suggestions for where to add screenshots. Each suggestion is marked with:
**Screenshot Suggestion:** [Description of what to show]
When screenshots are captured, update FAQ.md and other guides to include the image links.
Verification Checklist
When adding screenshots:
- Filename follows naming convention (kebab-case, descriptive)
- Image placed in correct subdirectory
- Alt text is descriptive (for accessibility)
- Image is high quality (PNG, 1920x1080 or smaller)
- Figure caption included in markdown
- Links work in both HTML and raw markdown views
- Mobile screenshots also included where relevant
- No sensitive information visible (passwords, keys, etc.)