site: plain-English demo up front, and a why-not-Cursor section - #189
Merged
Merged
Conversation
The hero led with the same zip signature used in the "Try it" code
block — accurate, but it meant even the FIRST thing a visitor saw
required already knowing Lex's type syntax, undercutting "you don't
have to learn Lex first" on its own page. Replaces it with a second
real, unedited recording whose actual typed request is plain English
("write a function that tells me if a word reads the same backwards,
like radar") — no signature, no Lex syntax to know going in.
Also adds a short "why not just use Cursor, Copilot, or Claude Code
directly" section: lex-code isn't pitched as a bigger IDE — it's a
plain CLI any of those can shell out to specifically for Lex, held to
a stricter bar (type-checked and closed against a declared acceptance)
than "the diff looks plausible."
The web UI screen recording moves into the "Try it" section (next to
the typed-issue example it's already showing), since the hero's new
recording is the first thing worth seeing now.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The web UI recording used the zip example again, and the typed-issue code block had no recording at all — text only. Two real, unedited replacements: - A new web UI session (password strength, not zip — more relatable, and it self-corrects a real syntax slip along the way) that also calls remember, then a second real turn to trigger reconciliation, so the Memory tab shows an actual promoted fact instead of the "No project memory stored yet" empty state the first recording had. - A live asciinema recording of the exact typed-issue commands already shown as a code block (same "add zip" issue, same run), ending in the same `verified` line — previously that flow was the one thing on the page not backed by a recording. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
zip[A, B]signature as the "Try it" code block — technically accurate but meant the very first thing a visitor saw already assumed Lex syntax, working against the page's own "you don't have to learn Lex first" pitch. Adds a second real, unedited asciinema recording whose typed request is plain English ("write a function that tells me if a word reads the same backwards, like radar") and puts it in the hero.Test plan
site/locally, confirmed both asciinema players load and play their respective real recordings🤖 Generated with Claude Code