SSWConsulting / SSWConsulting/SSW.Tiger

✨ Interactive Demo/Test - Create a test documentation page that allows a user to understand how Tiger works

Open
#79 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
2d 12h
Merged PRs (30d)
2

Description

Cc: @calumjs, @suiyangqiu

Hi Team,

Pain

There's no easy way for someone new to Tiger to understand how to test it. Adam wants a simple docs page that walks through the process.

Suggested Solution

Create a documentation page at SSWTiger.com/docs/how-to-test (or equivalent path on the Tiger website) that explains:

  1. How to record a meeting (or use a sample transcript)
  2. How to run Tiger on the transcript
  3. How to view the generated dashboard on dashboards.ssw.com
  4. Expected output and what to look for
Acceptance Criteria
  • Documentation page exists on the Tiger website
  • Covers the full test flow (record → process → view dashboard)
  • Includes screenshots or examples of expected output
  • Reviewed by Michael Q
More Information
  • As per @AdamCogan in Sprint 7 Review - Adam suggested creating this page so anyone can quickly test Tiger
  • Sprint 7 Review transcript (2026-04-13)

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Tiger website documentation entry point and the equivalent of /docs/how-to-test. Use a meeting recording or sample transcript to document the record → process → dashboard flow, including screenshots or examples of expected output from dashboards.ssw.com. The work is done when the page covers the full flow and has been reviewed by Michael Q.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.