Skip to content

use-case: Understand the platform quickly #99 #100#101

Open
bwalsh wants to merge 2 commits into
feature/marketing-speakfrom
feature/refactor-product-messaging
Open

use-case: Understand the platform quickly #99 #100#101
bwalsh wants to merge 2 commits into
feature/marketing-speakfrom
feature/refactor-product-messaging

Conversation

@bwalsh
Copy link
Copy Markdown
Contributor

@bwalsh bwalsh commented May 27, 2026

Summary

This PR refreshes homepage messaging in docs/index.md to better support translational researchers evaluating CALYPR.

The update replaces the abstract footer journey with a concrete Time-to-Decision Toolkit concept and tightens nearby section copy to reduce repetition and improve scanability.

Why

  • Make evaluation steps feel actionable and practical
  • Improve clarity around synthetic examples used in workflow demos
  • Strengthen narrative flow between walkthroughs, project catalog, and CTA footer

Addresses this use case:

### User Story: Understand the platform quickly

**As a** translational researcher  
**I want** to immediately see what the platform does  
**So that** I can determine whether it supports my research workflows

### Deliverables

- [ ] Replace abstract imagery with concrete product screenshots
- [ ] Add realistic workflow examples
- [ ] Create synthetic demo projects for screenshots
- [ ] Add examples of:
  - data exploration
  - project management
  - workflow execution
  - data integration
- [ ] Reduce abstract marketing copy
- [ ] Introduce concise value proposition messaging

### Acceptance Criteria

- Homepage contains at least 3 realistic screenshots
- Screenshots demonstrate actual workflows
- Primary value proposition visible above the fold
- Homepage messaging understandable without prior Calypr knowledge

Scope

Updated footer strategy (homepage)

Replaced prior “evaluation path” footer content with Time-to-Decision Toolkit framing:

  • Governance readiness check
  • Workflow portability audit
  • Data asset inventory template

Updated footer CTA labels:

  • Download toolkitExplore Tools
  • Schedule a 30-min walkthroughExamine sample datasets

Tightened nearby copy

In docs/index.md:

  • Eyebrow:
    • Workflow examplesTask walkthroughs
  • Workflow section H2:
    • Real tasks shown with synthetic demo projects.
      Common research tasks, demonstrated with synthetic projects.
  • Project section aria-label:
    • Synthetic demo projects used in homepage screenshots
      Synthetic project catalog
  • Project section eyebrow:
    • Synthetic demo projectsProject catalog
  • Project section H2:
    • These example projects power the screenshots above.
      These synthetic projects back the workflows above.

Files Changed

  • docs/index.md

Reviewer Guide

Quick pass (2–3 min)

  • Confirm footer now presents the Time-to-Decision Toolkit message
  • Confirm CTA labels are now:
    • Explore Tools
    • Examine sample datasets
  • Confirm tightened section labels/headings are present and non-redundant

Content pass (5–10 min)

  • Check tone alignment for translational researcher audience:
    • concrete
    • concise
    • non-salesy
  • Verify section flow:
    • Task walkthroughs → Project catalog → Toolkit CTA

Accessibility/semantics pass

  • Confirm updated aria-label remains descriptive and accurate
  • Confirm heading hierarchy remains unchanged

“Demo project” concept (for reviewers)

A Demo project is a curated, synthetic project used to demonstrate realistic end-to-end workflows without exposing real customer/patient data.

What it means in this page

  • Labels such as Demo project: TRX-101... indicate scenario-backed examples
  • The examples are synthetic by design
  • They are intended for demonstration, onboarding, and evaluation narratives

Backend Expectations (context for review)

This PR is copy-only, but the “Demo project” concept assumes:

  • Synthetic fixtures are versioned and reproducible
  • Demo projects are stable enough to keep screenshots/walkthroughs consistent
  • Demo projects respect role/access patterns similar to production behavior
  • Demo data remains isolated from production datasets
  • Workflow states/artifacts in demos are internally consistent for narrative fidelity
  • Demo environments can be reset for repeated walkthroughs

Non-goals in this PR

  • No backend/API/schema changes
  • No data fixture reseeding changes
  • No CTA destination routing changes (current footer CTAs still use href="#" placeholders)

Risk

  • Low (copy-only changes in homepage markdown)

Validation

  • Verified text updates in docs/index.md
  • Recommended: visual preview check for final tone and section flow

Follow-ups (optional)

  • Wire footer CTAs to concrete destinations:
    • Explore Tools → tools landing page
    • Examine sample datasets → sample dataset/project docs page
  • Consider adding a short glossary/tooltip for “Demo project” if stakeholders request stronger definition on-page

Copilot AI review requested due to automatic review settings May 27, 2026 18:44
@netlify
Copy link
Copy Markdown

netlify Bot commented May 27, 2026

Deploy Preview for calypr ready!

Name Link
🔨 Latest commit 78d19ae
🔍 Latest deploy log https://app.netlify.com/projects/calypr/deploys/6a176151d9fe610008a111a0
😎 Deploy Preview https://deploy-preview-101--calypr.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a71991a2e7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/index.md
Comment on lines +129 to +130
<a href="#" class="md-button md-button--primary">Explore Tools</a>
<a href="#" class="md-button">Examine sample datasets</a>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Restore real destinations for footer CTAs

When a homepage visitor clicks either new footer CTA, both links resolve to #, so they only stay on the current page instead of taking the user to tools or datasets. This regresses the previous footer CTAs, which linked to real site sections, and it is especially visible because Explore Tools has an existing tools landing page registered in zensical.toml/docs/tools/index.md; either wire these to real destinations or avoid rendering them as links until the destinations exist.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Refreshes the CALYPR docs homepage to make evaluation steps more concrete for translational researchers by replacing the prior footer journey with a “Time-to-Decision Toolkit” framing and restructuring the hero/workflow sections around task walkthroughs and a synthetic project catalog.

Changes:

  • Reworked homepage hero + workflow section into “Task walkthroughs” with screenshot-based panels and updated headings/labels.
  • Replaced the footer “evaluation path” with “Time-to-Decision Toolkit” messaging and updated CTA labels.
  • Added supporting CSS for new meta labels and homepage panel screenshots.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
docs/index.md Updates homepage structure/copy, adds walkthrough panels with screenshots, refreshes footer toolkit + CTA labels.
docs/stylesheets/extra.css Adds styling for usecase-panel__meta and homepage panel screenshots.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/index.md
Comment on lines +129 to +130
<a href="#" class="md-button md-button--primary">Explore Tools</a>
<a href="#" class="md-button">Examine sample datasets</a>
Comment thread docs/index.md Outdated
Comment on lines +43 to +56
<div class="business-hero__panel" aria-label="CALYPR product interface preview">
<img src="images/main-page.png" alt="CALYPR workspace showing project and data operations" loading="eager">
</div>
</section>

<section class="solution-section" aria-label="Proof and trust band">
<p class="eyebrow">Proof points</p>
<h2>Built on standards your bioinformatics and platform teams can verify.</h2>
<div class="value-grid">
<article>
<h3>Open standards foundation</h3>
<p>Data access on GA4GH DRS, execution through GA4GH TES, and metadata structures aligned to FHIR-oriented research workflows.</p>
<section class="solution-section" aria-label="Product workflow examples">
<p class="eyebrow">Task walkthroughs</p>
<h2>Common research tasks, demonstrated with synthetic projects.</h2>
<div class="solution-strip solution-strip--page">
<article class="usecase-panel">
<h3>1) Explore and organize research data</h3>
<p class="usecase-panel__meta">TRX-101 Lung Response Cohort</p>
<p>Browse study files and metadata, then filter assets by cohort and assay type before analysis kickoff.</p>
<img src="images/main-page.png" alt="Research project view for data exploration and project management" loading="lazy">
Comment on lines +1853 to +1859
.home .usecase-panel img {
width: 100%;
margin-top: 1rem;
border: 1px solid #dbeafe;
border-radius: 14px;
box-shadow: 0 14px 30px rgba(15, 23, 42, 0.12);
}
Comment on lines +525 to +536
.usecase-panel .usecase-panel__meta {
margin-top: 0.9rem;
color: #64748b;
font-size: 0.72rem;
font-weight: 700;
letter-spacing: 0.08em;
text-transform: uppercase;
}

.usecase-panel .usecase-panel__meta + p {
margin-top: 0.45rem;
}
@matthewpeterkort
Copy link
Copy Markdown
Contributor

matthewpeterkort commented May 27, 2026

1st set of cards The styling looks off on these cards, and the images in the cards are too small for the uninitiated user to know what they are. Remove numbering from cards perhaps.

“Complete a lightweight self-assessment in 20 minutes.” This sounds like “book a demo” but in more words.

I don't like the 2 separate card grids in the same page in the home page:
LLM feedback for alternative for 2nd set of cards :


A split-band explainer: left side = one strong buyer message, right side = 3 short proof points.
A comparison table: “Without CALYPR / With CALYPR” for speed, governance, reproducibility, handoff.
A timeline or workflow strip: show the buyer journey or procurement-to-production path instead of repeating boxed summaries.
A stacked benefit rows layout: each row has a headline, 1-2 sentences, and a small visual cue. Less noisy than cards.
A quote + metrics section: customer-style statement plus a few hard outcomes like setup time, auditability, portability.
A tabs/segmented control: if the content is for different audiences like buyers, engineers, stewards.
My recommendation: keep one card group only, and replace the other with stacked comparison rows or a split-band explainer. For a section called “Why buyers care,” those formats feel more decisive and less like a feature catalog.

A strong structure would be:

Hero/value statement
Why buyers care as 3 horizontal rows:
Lower platform risk
Faster vendor evaluation
Clearer governance and ownership
Follow with a small proof strip or quote
If you want, I can look at the homepage code in this repo and sketch 2-3 concrete replacement layouts for that section.

@bwalsh
Copy link
Copy Markdown
Contributor Author

bwalsh commented May 27, 2026

Remove numbering from cards perhaps.

Done

@bwalsh
Copy link
Copy Markdown
Contributor Author

bwalsh commented May 27, 2026

image image

@bwalsh
Copy link
Copy Markdown
Contributor Author

bwalsh commented May 27, 2026

Homepage UX + Infographic Update (follow-up)

Implemented a set of homepage improvements focused on large-screen rendering, infographic reliability, and Task walkthrough readability.

✅ What changed

Hero / infographic

  • Replaced hero panel image with docs/assets/infographic.svg in docs/index.md.
  • Moved infographic asset to:
    • docs/assets/infographic.svg
  • Embedded CALYPR logo inside the SVG as a base64 data URI (to avoid path resolution issues when rendered via <img> on home page).
  • Updated infographic styling/content:
    • Subtitle text:
      From study intake to analysis output with governed access
    • Removed numbered step circles.
    • Changed tools label from OPEN SOURCE TOOLS to TOOLS.
    • Matched ORGANIZE card styling to other flow cards.
    • Increased tool-chip contrast for readability (text, border, background).

Hero layout responsiveness (large monitors)

  • Rebalanced hero grid in docs/stylesheets/extra.css to give the panel/infographic more usable width.
  • Added large-screen media query (min-width: 1600px) to improve composition:
    • better column ratio
    • adjusted internal max widths
    • improved spacing/padding on ultrawide displays

Task walkthrough cards

  • Fixed awkward line breaks in card headings in the “Task walkthroughs” section:
    • Increased minimum card width in .solution-strip--page
    • Added heading wrapping rules (overflow-wrap, word-break, hyphens) for stable typography

📁 Files touched

  • docs/index.md
  • docs/assets/infographic.svg
  • docs/stylesheets/extra.css

🧪 Validation

Ran a full build successfully:

cd /Users/walsbr/calypr/attic/calypr.github.io
make build```


👀 Reviewer focus
* Home hero on large displays (ultrawide / 4k): copy-image balance and infographic size.
* Task walkthrough cards: heading wrapping and readability.
* Infographic rendering consistency in-browser + embedded homepage context.

@bwalsh
Copy link
Copy Markdown
Contributor Author

bwalsh commented May 27, 2026

Next steps #102

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants