View on GitHub

RaiseMyHand Documentation

Real-time classroom question system with live Q&A

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:

Instructions:

  1. Go to http://localhost:8000 or your production URL
  2. Don’t be logged in to anything
  3. Show full page with both student and instructor sections
  4. Desktop view

Why: Users need to see entry points


2. Student Interface - Question Submission

File: screenshot-student-view.png

What to show:

Instructions:

  1. Open student session in desktop browser
  2. Don’t submit anything yet (show clean state)
  3. Show the input box for questions
  4. Show vote buttons next to questions
  5. 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:

Instructions:

  1. Create a test session
  2. Submit several test questions with different vote counts
  3. Mark some as answered
  4. Screenshot with questions visible
  5. 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:

Instructions:

  1. Open student session on mobile phone
  2. Portrait orientation
  3. Show question list and voting
  4. At least 3-4 questions visible
  5. 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:

Instructions:

  1. Login as instructor
  2. Go to active session
  3. Make sure “All Questions” tab is selected
  4. Have at least 5-10 questions in session
  5. Desktop resolution (1920x1080)
  6. 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:

Instructions:

  1. Login as instructor
  2. Go to session with flagged questions
  3. Click “Flagged for Review” tab
  4. Submit a test question with profanity to create one
  5. Show the flagged question with buttons
  6. 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:

Instructions:

  1. Same setup as screenshot 6
  2. Hover over or show the approval buttons
  3. Make buttons visible and readable
  4. 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:

Instructions:

  1. Login as instructor
  2. Go to session dashboard
  3. Click “Show QR Code”
  4. Screenshot the QR code
  5. Make it large and clear
  6. 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:

Instructions:

  1. Go to instructor dashboard
  2. Click “Presentation Mode” or “View Stats”
  3. Screenshot the full screen
  4. Ensure text is large and readable
  5. 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:

Instructions:

  1. Login to admin panel with credentials
  2. Go to dashboard
  3. Screenshot main admin page
  4. Show navigation options
  5. Desktop resolution

Why: Administrators need to see management interface


11. Admin Panel - API Key Management

File: screenshot-admin-api-keys.png

What to show:

Instructions:

  1. In admin panel, go to API Keys
  2. Show list of existing keys
  3. Show “Create New API Key” button
  4. Screenshot the list view
  5. 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:

Instructions:

  1. Create a new API key in admin panel
  2. Screenshot the success screen
  3. Show the full key (can be fake/redacted)
  4. Show copy button
  5. 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:

Instructions:

  1. Open browser dev tools (F12)
  2. Go to Console tab
  3. Clear any existing logs: console.clear()
  4. Submit a question as student
  5. Screenshot showing new log entries
  6. 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:

Instructions:

  1. End a session in instructor view
  2. Go to “My Sessions”
  3. Find ended session
  4. Show “Download Report” option
  5. 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:

Instructions:

  1. Have QR code displayed on computer
  2. Use mobile phone camera to scan
  3. Screenshot the moment before clicking the notification
  4. Ensure QR code is in frame
  5. 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:

Instructions:

  1. Go to session join page
  2. Enter invalid session code
  3. Try to join
  4. Screenshot error message
  5. Desktop view

Why: Shows error handling is professional


Desktop Screenshots

Mobile Screenshots

QR Code Screenshot

File Naming Convention

Use this pattern for consistency:

screenshot-<feature>-<view>-<resolution>.png

Examples:

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

  1. Use real data - Submit actual test questions, don’t fake the UI

  2. Consistent styling - Use same browser, resolution, zoom level for all

  3. Show context - Include page titles, buttons, and navigation

  4. Clean slate - Close other windows/tabs to minimize distractions

  5. High contrast - Ensure text is readable in screenshot

  6. Test readability - Resize and view at different sizes to verify legibility

  7. Consistent timestamp - Take screenshots at similar times for consistent look

  8. Professional appearance - Use production domain names, clean test data

  9. Include variations - Show both empty states and populated states

  10. Mobile first - Prioritize mobile screenshots as mobile is increasingly important

Updating Screenshots

When to retake screenshots:

Accessibility

When creating screenshots:

Using Screenshots in Documentation

Template for including screenshots:

## Feature Title

Description of the feature.

![Student view with multiple questions](../screenshots/student-view/question-list.png)

**Figure 1:** Student interface showing question list with voting

### How to use this feature

1. Step one
2. Step two
3. Step three

![Admin panel API keys](../screenshots/admin-view/api-keys-list.png)

**Figure 2:** API Key management in admin dashboard

Always include:


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:

  1. instructor-login-page.png
    • Location: FAQ → “Getting Started”
    • Shows: API key entry field, login button
    • Purpose: Visual reference for where to paste API key
  2. session-creation-form.png
    • Location: FAQ → “Creating a Session”
    • Shows: Session title input, password field, create button
    • Purpose: Shows session creation interface
  3. 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:

  1. 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
  2. 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:

  1. 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
  2. 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:

  1. 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
  2. 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:

  1. 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
  2. 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:

  1. 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
  2. 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
  3. 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:

  1. 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
  2. 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):

Medium Priority (Important):

Low Priority (Nice to have):


How to Add Screenshots to Documentation

Once screenshots are captured, add them like this:

In Markdown:

![Description of screenshot](../screenshots/folder/filename.png)

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

Example:

![Instructor dashboard showing multiple questions](../screenshots/dashboard/instructor-dashboard-overview.png)

**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: