Cached public example
Open-source sample data is loaded by default so visitors can trust the output shape immediately, even before they paste their own repo.
Disco turns customer-visible commits into a polished changelog feed, hosted preview, and embeddable release surface. Paste a GitHub repo, see the shape instantly, then export the artifact or run it yourself.
The homepage preview mirrors the real artifact Disco produces: project context, overview metrics, grouped entries, themes, and optional source links. It is designed to make raw history feel legible and trustworthy before anyone installs anything.
Open-source sample data is loaded by default so visitors can trust the output shape immediately, even before they paste their own repo.
Generate a live-looking preview from a pasted repo URL, or open a cached example instantly. In either case the page keeps reinforcing the same promise: Disco gives you a real changelog artifact you can keep.
Disco is built to reflect shipped work, not just verbose history. The UI should make the contrast visible: raw git on one side, customer-facing narrative on the other.
fix: telemetry flush on worker
chore: migrate schema IDs
refactor: queue internals
debug: logging around auth
test: widget snapshots
Filters internal noise, isolates customer-visible work, and rewrites it into a changelog entry with themes, highlights, and optional source links.
Copy quality depends on a model being available. Output shape can drift, and the product feels uncertain.
Disco already groups, titles, summarizes, and emits stable artifacts without requiring AI. Optional enrichment sits on top.
Visitors read claims, but never see the actual object they’d get from the product.
The homepage itself becomes the first product experience: a changelog preview, an export shape, and a clear upgrade path.
The page should make Disco’s hybrid model obvious: a hosted preview and onboarding layer on top, a portable changelog engine underneath.
Paste a GitHub repo and route people into a hosted Disco preview that looks close to the eventual changelog page.
Reinforce that the output is portable: feed JSON, widget model, and rendered changelog surface that teams can embed or style.
Keep the OSS story visible: Disco can run in local git, in CI, or as part of a hosted workflow later.
These cards are designed to preload the preview experience, not just decorate the page. At least one cached open-source example should always be one click away from the hero.