Skip to content

screenshot-capture-guide.md

Latest commit

 

History

History
47 lines (35 loc) · 1.48 KB

screenshot-capture-guide.md

File metadata and controls

47 lines (35 loc) · 1.48 KB

Screenshot Capture Guide

Capture these assets after running the local app. The goal is to produce one recruiter-friendly pass and one deeper architecture pass.

Primary assets

  1. docs/assets/screenshots/workspace.png

    • workspace route
    • show agent chat, tool window, approvals, and artifacts in one frame

  2. docs/assets/screenshots/admin-dashboard.png

    • admin overview
    • include mock tools, workflows, and approvals

  3. docs/assets/screenshots/pilot-hub.png

    • pilot overview
    • include metrics, mock workflows, and pilot feedback cards

  4. docs/assets/screenshots/readiness-report.png

    • readiness route
    • capture the clearest enterprise-style report state

  5. docs/assets/screenshots/tool-execution-timeline.png

    • workspace or ops route
    • emphasize sequence, status, and visibility of actions

  6. docs/assets/screenshots/approval-flow.png

    • approval state with enough context for a reviewer to understand risk and action intent

GIF walkthrough

  • docs/assets/screenshots/org-ai-force-demo.gif
  • Target length: 15 to 25 seconds
  • Suggested sequence:
    1. workspace loaded
    2. open tool execution details
    3. show approval step
    4. switch to admin dashboard
    5. switch to pilot hub
    6. end on readiness report

Capture notes

  • Prefer desktop width around 1440px for primary screenshots.
  • Use the most populated mock data states, not empty shells.
  • Keep browser chrome minimal.
  • Avoid exposing any real secrets, tokens, or local machine identifiers.