From 302cceee36e5838097d6d28cf7f231dd348a1cd0 Mon Sep 17 00:00:00 2001 From: Benjamin Scott Date: Fri, 15 May 2026 15:51:51 -0600 Subject: [PATCH 1/2] Add landing page content for helio-cli marketing site MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Standalone landing page copy positioned around "the fastest way to launch a UX test." Targets developers (primary CTA: npm install) with a secondary lane for UX researchers and PMs. Pure markdown content for handoff — no HTML, no styling, designer/dev notes inline as comments. Co-Authored-By: Claude Opus 4.7 --- marketing/helio-cli-landing.md | 253 +++++++++++++++++++++++++++++++++ 1 file changed, 253 insertions(+) create mode 100644 marketing/helio-cli-landing.md diff --git a/marketing/helio-cli-landing.md b/marketing/helio-cli-landing.md new file mode 100644 index 0000000..d3ad6b8 --- /dev/null +++ b/marketing/helio-cli-landing.md @@ -0,0 +1,253 @@ + + +# Ship a UX test before your coffee's done. + + + +Helio CLI puts the full Helio research platform behind a single command. Create a test, attach standardized UX metrics, send it to a real audience, and pull results — without leaving your terminal. Built for developers who automate, researchers who move fast, and teams who want their UX work to live in the same workflow as their code. + +No new dashboard to learn. No new login to keep open. Same Helio platform you already trust — exposed as commands you can pipe, script, and version-control. + + + +**`npm install -g helio-cli`**     [Read the quickstart →](#try-it-now) + +```bash +$ helio-cli tests create \ + --project-id 1f2e... \ + --name "Checkout sentiment check" \ + --intro "Two quick questions about checkout." \ + --target-audience-size 50 \ + --ux-metrics sentiment loyalty + +Test draft created · 9c3b-...-4a21 + +$ helio-cli tests send 9c3b-...-4a21 + +Live. Responses streaming. +``` + +--- + +## The 60-second story + +You already installed it (above). Here's what the next 60 seconds look like. + + + +**1. Authenticate once.** + +```bash +helio-cli auth login +``` + +Paste your API ID and token from `my.helio.app/account/organization`. The CLI remembers you. + +**2. Create and send a test, with UX metrics auto-generated.** + +```bash +helio-cli tests create \ + --project-id \ + --name "Homepage hero test" \ + --intro "Help us evaluate the new homepage." \ + --target-audience-size 50 \ + --ux-metrics sentiment appeal usefulness + +helio-cli tests send +``` + +That's the whole demo. Two commands, one live UX test, results streaming in within minutes. + +--- + +## What it does + + + +**Create tests, all ten question types.** +```bash +helio-cli tests create --questions '[...]' +``` +Free response, multiple choice, likert, NPS, ranking, preference, matrix, card sort, point allocation, and max-diff. Define your test in JSON, validate it with `--dry-run`, ship it when it's right. + +**Auto-generate UX metrics.** +```bash +helio-cli tests create ... --ux-metrics sentiment loyalty usefulness +``` +Eleven standardized metrics, attached to any test with a single flag. Customize the context, keep the wording consistent, benchmark across studies. + +**Pull reports.** +```bash +helio-cli tests report --include questions_summary,demographics,ux_metrics +``` +Summary stats, full response data, demographics filters, pagination, prototype journeys. Output as text for humans or JSON for pipelines. + +**Manage participants and custom lists.** +```bash +helio-cli custom-lists add-participants --data '[...]' +``` +Bulk-add participants via JSON, manage custom lists, target specific audiences for repeat studies and longitudinal work. + +**Edit drafts before they go live.** +```bash +helio-cli tests add-question --type likert --instructions "Checkout was easy." --scale-type agreement +``` +Add, edit, remove, and reorder questions on any draft test. Preview the participant view before you spend an incentive. + +**Run in CI.** +```bash +HELIO_API_ID=$ID HELIO_API_TOKEN=$TOKEN helio-cli tests list --output json +``` +Environment-variable auth, structured JSON output, predictable exit codes, `--dry-run` validation, and a built-in `doctor` command to diagnose issues fast. + +--- + +## UX metrics, generated for you + + + +Every test type Helio offers can include standardized UX metrics — sentiment, loyalty, usefulness, appeal, comprehension, expectations, and more. The CLI generates them for you, with consistent wording, so results are comparable across tests, products, and quarters. + +A UX metric isn't just a question. It's a calibrated instrument with documented scales, baselines, and behavior across thousands of Helio studies. When you add `--ux-metrics sentiment loyalty` to a test, you're not writing a survey — you're plugging into a measurement system. That means a sentiment score from this week's release can be compared, honestly, to one from a year ago. + +```bash +helio-cli tests create \ + --project-id \ + --name "Onboarding pulse" \ + --intro "A quick check on first-run experience." \ + --target-audience-size 75 \ + --ux-metrics sentiment loyalty usefulness \ + --ux-metric-context "the Helio onboarding flow" +``` + +Use the metric, every time. Benchmark against yourself, across releases, without rewriting questions from scratch. + + +Available: `sentiment`, `feeling`, `appeal`, `reaction`, `comprehension`, `frequency`, `loyalty`, `intent`, `desirability`, `usefulness`, `expectations`. + +--- + +## Built for automation + + + +**JSON everywhere.** Add `--output json` to any command. Pipe the result into `jq`, your data warehouse, a notebook, or a script. Every command in the CLI honors the same flag, so your tooling only has to learn one contract. +```bash +helio-cli tests report --output json | jq '.questions_summary' +``` + +**Environment-variable auth.** Drop into CI or a sandbox without touching a config file. +```bash +export HELIO_API_ID=... +export HELIO_API_TOKEN=... +helio-cli tests list --status running --output json +``` + +**Structured errors, predictable exit codes.** Errors come back as JSON when you ask for it. +```bash +{ "error": "Unauthorized", "code": 401 } +``` + +**`--dry-run` before you spend.** Validate a test payload without creating anything or charging incentives. +```bash +helio-cli tests create --dry-run --project-id --name "Test" --intro "Hi" \ + --target-audience-size 50 --questions '[...]' +``` + +Wire it into GitHub Actions, internal tools, or your nightly cron. The CLI is built to be scripted, not just typed. + +--- + +## Two ways in + + + +**For developers.** +You already live in a terminal. Now your research does too. Schedule nightly pulls, gate releases on sentiment thresholds, version-control your test definitions next to the code they evaluate. Treat user feedback like every other production signal — observable, scriptable, and tied to a build. + +```bash +# nightly: pull the latest report and post to Slack +helio-cli tests report $TEST_ID --output json \ + | jq '.ux_metrics' \ + | ./post-to-slack.sh +``` + +**For researchers and PMs.** +Save a test once, run it a hundred times. Re-run last quarter's onboarding study against a fresh audience — no clicking through screens, no re-typing instructions, no losing the wording you spent two weeks tuning. The test definition is a file you can share, edit in a PR, and replay forever. + +```bash +# re-launch the onboarding study with a new audience +helio-cli tests create \ + --project-id $PROJECT \ + --name "Onboarding · Q3 wave" \ + --intro "$(cat onboarding-intro.txt)" \ + --target-audience-size 100 \ + --ux-metrics sentiment loyalty +``` + +Same platform you know. Faster surface to work on. The web app is still there when you want it; the CLI is there when you need to move. + +--- + +## Try it now + +1. **Install.** + ```bash + npm install -g helio-cli + ``` + +2. **Log in.** + ```bash + helio-cli auth login + ``` + +3. **See what's there.** + ```bash + helio-cli projects list + ``` + +4. **Launch your first test.** + ```bash + helio-cli tests create \ + --project-id \ + --name "My first CLI test" \ + --intro "Quick feedback on a new idea." \ + --target-audience-size 50 \ + --ux-metrics sentiment + ``` + +For a guided walkthrough and full command schemas: `helio-cli guide`. + +For everything else: the [GitHub repo](#) and the [API reference](#). + + + +--- + +## Helio CLI is open and ready. + +```bash +npm install -g helio-cli +``` + +[Docs](#) · [API reference](#) · [Support](#) · [Status](#) + + + +Requires Node.js ≥ 22 and a Helio API token. Get yours at [my.helio.app/account/organization](https://my.helio.app/account/organization). From d47a27b24872b7fca2d028e7d093e8cca0035fa6 Mon Sep 17 00:00:00 2001 From: Benjamin Scott Date: Fri, 15 May 2026 16:00:48 -0600 Subject: [PATCH 2/2] Address landing page review: package name, real output, accurate copy - Update install command to @zurb/helio-cli (matches the published package name on the rename branch); binary on $PATH is unchanged - Replace invented terminal output in the hero with realistic printKeyValue() output that matches src/output.ts - Soften unverified "results streaming in within minutes" claim - Fix command count in the 60-second story (3, not 2) - Drop prototype_journeys from the reports prose since the adjacent code example doesn't demonstrate it Co-Authored-By: Claude Opus 4.7 --- marketing/helio-cli-landing.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/marketing/helio-cli-landing.md b/marketing/helio-cli-landing.md index d3ad6b8..abb472d 100644 --- a/marketing/helio-cli-landing.md +++ b/marketing/helio-cli-landing.md @@ -2,7 +2,8 @@ helio-cli landing page — content document Audience: developers first, UX researchers and PMs second. -Primary CTA: npm install -g helio-cli (used exactly 3 times: hero, quickstart, footer). +Primary CTA: `npm install -g @zurb/helio-cli` (used exactly 3 times: hero, quickstart, footer). +Binary on $PATH is still `helio-cli` — all other commands on this page use it unchanged. Positioning: the fastest way to launch a UX test — idea to live, under a minute, from your terminal. Voice: action-first, every claim backed by a one-liner, no marketing fluff. @@ -23,7 +24,7 @@ No new dashboard to learn. No new login to keep open. Same Helio platform you al -**`npm install -g helio-cli`**     [Read the quickstart →](#try-it-now) +**`npm install -g @zurb/helio-cli`**     [Read the quickstart →](#try-it-now) ```bash $ helio-cli tests create \ @@ -33,11 +34,14 @@ $ helio-cli tests create \ --target-audience-size 50 \ --ux-metrics sentiment loyalty -Test draft created · 9c3b-...-4a21 +id 9c3b-...-4a21 +name Checkout sentiment check +status draft $ helio-cli tests send 9c3b-...-4a21 -Live. Responses streaming. +id 9c3b-...-4a21 +status live ``` --- @@ -69,7 +73,7 @@ helio-cli tests create \ helio-cli tests send ``` -That's the whole demo. Two commands, one live UX test, results streaming in within minutes. +That's the whole demo. Three commands, one live UX test, responses landing as participants complete. --- @@ -93,7 +97,7 @@ Eleven standardized metrics, attached to any test with a single flag. Customize ```bash helio-cli tests report --include questions_summary,demographics,ux_metrics ``` -Summary stats, full response data, demographics filters, pagination, prototype journeys. Output as text for humans or JSON for pipelines. +Summary stats, full response data, demographics filters, and pagination. Output as text for humans or JSON for pipelines. **Manage participants and custom lists.** ```bash @@ -209,7 +213,7 @@ Same platform you know. Faster surface to work on. The web app is still there wh 1. **Install.** ```bash - npm install -g helio-cli + npm install -g @zurb/helio-cli ``` 2. **Log in.** @@ -243,7 +247,7 @@ For everything else: the [GitHub repo](#) and the [API reference](#). ## Helio CLI is open and ready. ```bash -npm install -g helio-cli +npm install -g @zurb/helio-cli ``` [Docs](#) · [API reference](#) · [Support](#) · [Status](#)