Skip to content

feat(site): let a visitor run Drift in a browser, on their ecosystem - #246

Merged
RodolpheKouyoumdjian merged 1 commit into
mainfrom
feat/browser-demo
Sep 9, 2026
Merged

RodolpheKouyoumdjian merged 1 commit into
mainfrom
feat/browser-demo

Conversation

@RodolpheKouyoumdjian

Copy link
Copy Markdown
Collaborator

The landing page had no way to try the tool. Everything it offered was something
to watch — a recording, a benchmark, a support matrix — and the one question a
sceptical reader has ("does it do my language, on my code") was answered
with a JavaScript recording and a promise about the rest.

What this adds

A "Run it yourself" section, placed immediately after the recorded run where
that scepticism peaks, linking a prepared Codespace per ecosystem — plus a
"Try it in your browser" hero CTA.

Each fixture in trydrift/demo is committed at an old dependency version with
source written for it; Codespace creation upgrades the manifest and touches
nothing else. So Drift analyses an ordinary uncommitted change and has no idea
it is a demo — git status in the Codespace shows one modified manifest, which
is the claim, checkable in the demo itself.

Keeping the two lists honest

demos.ts duplicates only the package and the two versions. Labels come from
the generated capabilities.ts, and demos.test.ts asserts the demo set
equals the supported-ecosystem set — so adding an ecosystem to the core fails
this build until a demo exists. The failure mode otherwise is silent, and in the
direction that undercounts what Drift does.

drift.ui.openOnStartup

New extension setting, default false, which reveals the panel as a window
opens — before the startup analysis rather than after, so a visitor watches the
analysis happen instead of arriving at a finished verdict. Prepared environments
(demos, walkthroughs) are what it exists for; seizing the sidebar of every
window is how an extension gets uninstalled. The default is pinned by a test.

Verification

npm run release:check passes all 13 gates on this branch — including the
packed-CLI clean-install smoke test, the site production build, and the
docs/identifier check.

Companion PR: trydrift/demo#21.

🤖 Generated with Claude Code

The landing page had no way to try the tool. Everything it offered was
something to watch — a recording, a benchmark, a support matrix — and the one
question a sceptical reader has ("does it do *my* language, on *my* code") was
answered with a JavaScript recording and a promise about the rest.

A "Try it yourself" section now links a prepared Codespace per ecosystem, placed
immediately after the recorded run, where that scepticism peaks. Each fixture is
committed at an old dependency version with source written for it; Codespace
creation upgrades the manifest and touches nothing else, so Drift analyses an
ordinary uncommitted change and has no idea it is a demo.

The demo list duplicates only the package and the two versions. Labels come from
the generated capability list, and a test pins the demo set against it, so
adding an ecosystem to the core fails this build until a demo exists — the
failure mode otherwise is silent and undercounts what Drift does.

`drift.ui.openOnStartup` (off by default) opens the panel as a window opens,
before the startup analysis rather than after, so a visitor watches the analysis
happen instead of arriving at a finished verdict. Prepared environments are what
it exists for; seizing the sidebar of every window is how an extension gets
uninstalled.

Co-Authored-By: Claude Opus 5 <[email protected]>
Copilot AI lite review requested due to automatic review settings September 9, 2026 21:32

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@RodolpheKouyoumdjian
RodolpheKouyoumdjian merged commit deb8a32 into main Sep 9, 2026
6 checks passed
@RodolpheKouyoumdjian
RodolpheKouyoumdjian deleted the feat/browser-demo branch September 9, 2026 21:39
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.

2 participants