Skip to content

feat(river): simplify hero headline to "Group chat without the company in the middle"#66

Merged
sanity merged 1 commit into
mainfrom
feat/river-h1-drop-familiarity
Jul 4, 2026
Merged

feat(river): simplify hero headline to "Group chat without the company in the middle"#66
sanity merged 1 commit into
mainfrom
feat/river-h1-drop-familiarity

Conversation

@sanity

@sanity sanity commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Problem

The hero H1 "Group chat you already know. / Without the company in the middle." leads with a familiarity claim that reads as slick, 1960s-ad-style marketing and presumes what the reader already knows.

Approach

Lead the headline with the differentiator: "Group chat without the company in the middle." (the last phrase in brand blue). The Signal/WhatsApp familiarity that "you already know" was reaching for is still carried by the subhead directly below ("River feels familiar, like Signal or WhatsApp…"), so the orientation is preserved, just moved a line down. Also removes the now-unused .rv-h1-2 CSS rule.

Testing

Hugo build clean; verified the new H1 renders (desktop + iPhone) with correct dark/blue split, and the old copy and dead class are gone. Copy-only change to one template + one dead CSS rule; no logic.

Wording chosen by Ian.

[AI-assisted - Claude]

…y in the middle"

Drop "Group chat you already know" — it read as slick ad copy and
presumes what the reader knows. Lead the headline with the differentiator
instead; the Signal/WhatsApp familiarity is still carried by the subhead
right below it. Also removes the now-unused .rv-h1-2 CSS rule.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q5nGtN2vVKqYABT5sosrAB
@sanity sanity merged commit d01b9cc into main Jul 4, 2026
3 checks passed
@sanity sanity deleted the feat/river-h1-drop-familiarity branch July 4, 2026 15:32
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.

1 participant