Landing Page Variations

Five reviewable homepage directions for Parity. Each keeps the product message centered on matched coverage: how much a single test covers the file it belongs to.

Recommended base

Use Ledger as the homepage spine, then borrow Developer for the quickstart section.

The strongest public positioning is “coverage reconciled file by file.” It explains the category quickly, demonstrates the matched-coverage concept visually, and still leaves room for a command-first section below the fold.

01LedgerStripe-like executive proof, with matched coverage as a source/test ledger.02DeveloperCommand-first quickstart for engineers who want to see the config and output immediately.03ManualDocumentation-first operating manual with a clear install, configure, enforce path.04LabSample-app showcase built around PHPUnit, Pest, Jest, Mocha, Vitest, and Rust.05CI RoomRelease-gate narrative focused on the exact failure a reviewer needs to fix.

VariationBest forRiskHomepage fit

LedgerExplaining matched coverage in one glance.Needs a quickstart section to convert developers.Highest

DeveloperEngineers evaluating install friction.Less emotionally distinctive as a brand page.High

ManualDocumentation-led onboarding and DevOps handoff.Feels more like docs IA than a homepage.Medium

Sample LabShowing breadth across stacks and test tools.Better as a secondary proof section.Medium

CI RoomRelease managers and teams with merge gates.Narrower than the full product story.Medium