Skip to content

Create documentation - #1

Open
jennifer-bowser wants to merge 18 commits into
mainfrom
create-documentation
Open

Create documentation#1
jennifer-bowser wants to merge 18 commits into
mainfrom
create-documentation

Conversation

@jennifer-bowser

@jennifer-bowser jennifer-bowser commented Aug 31, 2026

Copy link
Copy Markdown

Here's the documentation I've created for the demo site to explain to grant reviewers how to use VarCat. The files are numbered to indicate the order in which they are designed to be read.

I'd LOVE feedback, especially on the following:

  • Is any information missing?
  • Are any parts too verbose and/or repetitive?
  • Does the way in which the information is organized make sense?
    • e.g., splitting the info into 2 documents, the flow of information within each document individually, etc.
  • Presentation: does it make sense to leave these as markdown files, or should I use something like mkdocs to create a small read-the-docs-type website à la the gkm starter kit?

@jennifer-bowser jennifer-bowser self-assigned this Aug 31, 2026
@jennifer-bowser
jennifer-bowser marked this pull request as ready for review September 2, 2026 14:06
@jennifer-bowser
jennifer-bowser requested review from ahwagner and korikuzma and removed request for ahwagner and korikuzma September 2, 2026 14:07

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worthwhile explaining when you would use Not Applied and Not Assessed. The other applications are guideline specific but I don't know if its intuitive of why something would be in the not applied or not assessed category

@korikuzma

Copy link
Copy Markdown
Member

@jennifer-bowser Could you put a priority label on this (asking so I know when I need to review by)

@jennifer-bowser jennifer-bowser added priority:medium Medium priority priority:low Low priority and removed priority:medium Medium priority labels Sep 3, 2026
@korikuzma

Copy link
Copy Markdown
Member

Presentation: does it make sense to leave these as markdown files, or should I use something like mkdocs to create a small read-the-docs-type website à la the gkm starter kit?

I haven't done a deep dive on what you wrote, but I would recommend linking to these files in the repo README if you don't want to go the mkdocs route. I would guess most people would not look in the documentation folder

@korikuzma korikuzma left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great first pass @jennifer-bowser ! Made some suggestions on things that could be added to make the tutorial more thorough.

IMO, I would prefer a GH pages site using Zensical (apparently mkdocs is no longer maintained). GKM-Starter Kit has been updated with this migration.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Consider adding images of what these concepts look like in the UI

## Assessment Statuses
Assessments move through a lifecycle of the following statuses:

1. `Pending`

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: I know it's kind of self explanatory, but we should state what these statuses mean. Also how the demo handles Reviewed (since in somatic, we only allow clinical directors to perform review)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General comments on images: Some of these are outdated with the latest changes in demo site, I'd recommend updating for consistency (could be a separate ticket if we're expecting more changes). For example, we no longer have an avatar / include emails for users

- _Move_ the assessment to the next or previous status
- _Overtake_ an active assessment from another user
- _Review_ the assessment's status history, including _who_ previously checked out the assessment and _when_
3. The **summary modal** lists the assessment's assertions (left) and displays a summary of the selected assertion (right), including its:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Did we want to add in editing an assertion?

- _Applied Evidence_: A summary list of the evidence currently contributing to that result
4. **Evidence tabs** contain the evidence for each assertion type.
5. The **table of contents sidebar** allows quick navigation to the various sections of the assessment.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion:

  1. Info tab?

Made this note in the agenda:

Kind of related. https://github.com/GenomicMedLab/igm-varcat-ui/issues/1228 (can make it a general update the info panel ticket; if we're going to have the info panel showing we should update the docs here)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: May also want to call out the user dropdown if we want to include everything.

Separate concern that can be handled in a separate issue: Demo version does not display (should we just remove or hardcode so people aren't confused about a lonesome #)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Do we want to display the history revisions?

Comment on lines +52 to +57
Review each evidence section and update it as needed. You can:

- Curate your own additional evidence manually
- Revise the section's auto-selected code
- Change the section's auto-computed score

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Did we want to include a screenshot of the rationale modal?


![Variant evidence view](/documentation/images/case-control-variant.png)

If needed, add new evidence with **Add Evidence**.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Did we want a tutorial on walking through the add evidence modal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority:low Low priority

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants