Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
10 KiB
/learn — James-eye review
Verdict: 7/10 Ready: 8 Nov, copycheck missing 0 of 43 (live hanzo.ai). The blog post titles (lead, Kai, "Your AI is Planning To Kill You"), the "Read the thinking" titles and the card/row titles are now span leaves instead of (same type, hover underline kept; the Kai title is the link's own text). taste/unique OK; 0 console errors, no overlap at 1470x801 and 375x812. Dark: 8 Nov, matches live hanzo.ai in dark side by side (docs/gallery/learn/dark-*.jpg); darkcheck OK, lightcheck OK, copycheck 0. (darkcheck's one remaining item is intended: the map's train, the current stop, is a light fill as live's selected pill. Rules under html:not(.light) in Hanzo's tokens; the blog room ([data-room=dark]) stands as it is. Live's hero halftone is drawn in dark only (shared HeroDither, Hanzo's own Dither), so bright mode is unchanged.) First complaint: "The map at the top is lovely, then I scroll and there's a whole screen of nothing, then a row of grey boxes with big numbers in them. That's the lazy look. And it just stops at the questions; where's the ask at the end?"
Walked: 7 Nov 2026 (session clock), dev server, route warmed first. 1470x801 (wheel in 8 steps per screen, dwell ~2 s, frame diffs at rest, video recorded) and 375x812 (isMobile, touch; CDP touch swipes of ~780px, one real screen per step, dwell and frame diffs). Hover with fine pointer emulated via CDP ((hover: hover) confirmed true). Clicked and keyed the stations, stepped/dragged/threw the rail, swiped it on phone, paused and resumed both films, hovered/opened FAQ items and deep-linked #q-how-much-does-it-cost-to-use. Checked 320 width, 375x667 fold, reduced motion, JS off, CLS, console. parity.py /learn: 69/69 text, 26/26 links. taste.py on Learn.jsx/.css: OK.
The 11 answers
- Sells in 5 s / moves within 1 s? Sells: "Learn Hanzo" (52px, baseline at 316px = 39% of 801), lede, solid "Get started" all in the first screen at both sizes (phone CTA bottom at 295px, also above the fold at 375x667). Within 1 s only the arrival plays (h1 line cut-in, side and map fade-ups). The live object, the train, makes its first move at 2.8 s (
setTimeout(…, 2800)), not "within a second" as the coverage card claims. It then rides to MCP and stops; at ~14 s the hero frame diff is 0.0000. - One in, one out, or a document? Mostly scenes, but the desktop seam between the map and the rail is a dead screen: at scrollY 720 about 330px of empty white sits between the map's foot and "Pick what to try" (hero bottom padding up to 200px plus section padding). The Questions screen and everything after it are fully still (rest diff 0.0000 at desktop screen 5 and phone screens 5–9). No closing ask: Questions runs straight into the footer.
- A real visual object in every section? Hero: yes, the transit map is a real, working object. Go further: yes, Zen's film (720px, 8 s, loops, pausable). Dark room: Kai's film in the third post, but the 44px lead post is a 440px-tall #171717 slab whose top half is empty. "Pick what to try": six grey #f5f5f7 tiles, each a 64px grey numeral over a big empty middle and a title. A numeral is not a product visual; it reads as placeholder cards. "Read the thinking": three text links. Questions: the 64px number, fine.
- One ask, sticky, nothing floating; scale rhythm? Good. Header ask is outlined while the hero's "Get started" is visible, then turns solid and relabels "Get started" (desktop). One solid per viewport measured on the first screen. Nothing of the page floats over content (the cookie card is site chrome; on phone it covers about the bottom 220px). Rhythm mostly holds: one 52/64/44px thing per screen with 21px titles and 16px body. Exception: the rail shows four 64px numerals at once, so it is the one screen where everything is the same size.
- Every hover and press answers, no jumps? Mostly. Hero CTA bg #0a0a0a to #2c2c2e. University link arrow +4px. Stations: ring inks. Guide arrow translate(3,-3). Rail card: numeral inks and lifts 4px, title underlines (the tile fill does not change: card and hover both resolve to #e8e8ed after the idle ink). Rows and thinking arrows move 4px. Film cards scale video 1.03. Presses use scale .97. Rail: Next steps 327px ("02 / 06"), a mouse throw went 327 to 627 to 795 px with inertia and fired no click, a phone touch swipe moved 300px. Stations: click and ArrowLeft/Right work, focus follows. Bug: hovering an FAQ question underlines the whole button, and that underline is drawn under the "+" glyph too, so the open state's 45° rotation renders as a broken "\x" icon while the pointer is still on it (screenshot
faq-icon.png). Cause:.xlr-qa .x-faq button:hover { text-decoration: underline }reaching the<i>. - Overlaps, font swap, layout shift? CLS 0.0004 desktop and 0.0011 phone, both tiny. No horizontal scroll at 375 or 320 (scrollWidth 320). No overlap of h1, CTA or nav. In the first desktop load the dev badge showed "1 Issue" (React hydration attribute mismatch). It did not come back in 4 later loads at 1470 and 375 with 0 console errors, so it is intermittent, likely from parallel edits or shared chrome, but someone should check it. Reduced motion: the train stays on 01, only one
xp-cutanimation is left, final state shown. JS off: h1 and all copy legible. - Which reference, and is its motion there? Closest is osply/hamol in its editorial restraint plus an Apple-style one-object hero. The pointer and state micro-motion is real (throwable rail, the pointer-following question number, station tabs). Nothing from synchronized.studio (the rail cards carry
data-morph, but nothing visibly opens into a page here). No pinned scene, no scrub. - Different from neighbours? Yes. A transit map with a riding train is its own hero medium and signature; no other page I know of uses it.
- 18 parts? See below. The main gaps: no closing
Band/ask, fade-up budget, FAQ hash sync is one-way, no 4+ media block. - Banned tells? No hue, gradient text, Inter, emoji, stripe or kicker over the h1. Borderline: "Read the thinking" is three equal columns in a row (unboxed, but it reads as the banned trio), and the map is outlined and holds a raised filled panel (MASTER 7: raise or outline, never both). Site-wide note, not this page's fault: the greys in use are Apple's (#f5f5f7, #e8e8ed, #6e6e73, #86868b, #a1a1a6, #2c2c2e from
app/globals.css/system.css), not the deck ramp (#f5f5f5, #ededed, #737373, #525252). No hard banned tell found, so no cap applies. - Copy untouched? Yes: parity 69/69 text, 26/26 links. Title "Learn Hanzo — Hanzo AI", canonical https://hanzo.ai/learn/.
Missing from the 18 parts
- Part 3: no closing
Band; the page ends on the FAQ with no ask. The card says the live page has none, but the existing "Get started" label in a closing strip is not new copy. Something moves within 1 s: only the arrival does; the train waits 2.8 s. - Part 8/9: fade-up budget broken. The hero side (opacity+y16), the map (opacity+y32), every station panel swap (opacity+y24) and the kit
FaqRiseper item make 3+ fade-ups against a limit of 2. The kit FAQ also animatesheight. - Part 6:
#q-slugopens on load (verified), but clicking a question does not update the hash: the hash stayed on the previous value after opening another question. - Part 7: the map is outlined and has a filled panel inside it (raise or outline).
- Part 10: only 2 films on the page; no block of 4+ real Hanzo media, though the TRY items (Chat, Playground, Dev, Zen, MCP, Agents) all have Hanzo renders or model media.
- Part 11: on phone the station names are visually hidden (
.xlr-stops button spanclipped under 900px), so the hero object is five unlabeled dots. The map only makes sense once you read the panel. - Part 15 (Morph):
data-morphis on rail/row titles, but none of the targets visibly opens from the card in this walk.
Fixes (in order)
- Kill the dead screen after the map (desktop).
.xlr-hero { padding-bottom: clamp(120px,14vw,200px) }→ aboutclamp(56px,6vw,88px), and pull.xlr-indexpadding-top down so "Pick what to try" peeks about 56px under the map at scrollY ≈ 700. Target: no 1470x801 screen with more than ~150px of empty paper. - Give the rail cards a real object. In
.xlr-card, replace the empty 1fr middle with each product's own Hanzo visual (the existingcomponents/render/UI for Chat/Playground/Dev, the Zen and Agents model media throughFilm/Pic, the MCP terminal line) at true size, cropped. Drop the numeral to 32px, or keep 64px only on the lit/hovered card so one numeral is big at a time. This also gives the page its 4+ real media block. - Add a closing ask. After
Questions, add the kitBandwith the existing "Get started"Cta(data-cta="learn.band") and the Hanzo University link, so the page ends on the ask and not on a still FAQ. - Fix the FAQ icon glitch. Scope the underline to the text:
.xlr-qa .x-faq button:hover > span { text-decoration: underline … }instead of the wholebutton, so the rotated "+" never carries an underline stroke. - Make the hero alive within 1 s and keep it breathing. First train step at ~900 ms instead of 2800 ms, and give the resting state one quiet idle move, e.g. the current station's ring breathing opacity .16 to .3 over 3 s, or the train idling 2px. Stop it on reduced motion.
- Get within the 2 fade-up budget. Make the hero side and map arrive by clip/line mask, or let only the map rise. Change the station panel swap to a horizontal clip-path wipe in the train's direction (300 ms, ease-emphasis), not opacity+y24.
- Phone map labels. Under 900px show the current station's name under the train (one 13px label that slides with it), or a 12px Zen Mono label under each dot, so the five dots read as a line of guides.
- Lead post needs its object. Give
.lead .xlr-postthe post's own hero media (the headless-commerce post image, mirrored topublic/) in the empty top half, or cut itsmin-height: 440pxto its content height. - Raise or outline the map, not both. Remove the
.xlr-mapoutline, or make.xlr-panelsa hairline-divided area instead of a #f5f5f7 fill. - "Read the thinking" trio. Break the equal 3-up: make it a hairline row list (like
.xlr-rows), or an 8/5 split with Source as the single larger item. - Hash sync: on FAQ toggle,
history.replaceState(null,'','#'+slug)(kit request if it has to live inFaq). - Shared, for the conductor: site greys are Apple values (#f5f5f7/#6e6e73/#e8e8ed), not the deck ramp. Also check the intermittent hydration "1 Issue" badge seen on first load.