Skip to content

Demo: Add Operations Workbench screenshots to README/demo docs #118

@smithaldon1

Description

@smithaldon1

Purpose

Make the project look credible and understandable before live demos.

Parent Epic

#14

Acceptance Criteria

  • Add screenshots or screenshot placeholders once UI exists.
  • Demo docs include screenshots for Overview, Detection detail, Evidence timeline, Recommendation review, and RCA/CAPA draft.
  • README or docs link to the demo runbook.
  • Screenshots are clearly marked as simulator-backed demo.
  • Screenshots do not imply production deployment or real plant data.

Dependencies

Out of Scope

  • Marketing website.
  • Long-form case study.
  • Customer logos or real plant screenshots.

Test Plan

  • Verify image paths render in Markdown locally/GitHub.
  • Confirm screenshots match the current demo UI.
  • Confirm simulator-backed labeling is visible in docs.

Documentation Impact

  • Update README or demo docs with screenshots and runbook link.
  • Update docs/LEARNING_LOG.md when implemented.

Suggested Labels

documentation, operations-workbench, demo-polish, manufacturer-demo, demo-ready

Suggested Milestone

Demo Ready: Operations Workbench

Metadata

Metadata

Assignees

No one assigned

    Labels

    Taskdemo-polishPolish work after core demo path existsdemo-readyDemo readiness scopedocumentationDocumentation workfrontendFrontend application workmanufacturer-demoSupports the manufacturer-facing demo narrativeoperations-workbenchOperations Workbench web UI workready-to-buildReady for contributor implementation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions