Files
Claude 07cf81bd47 Handoff layout: new README; build-chat notes moved to docs/build-notes/
- README.md: what this is, how to run and build it, the folder map, how light and dark
  mode work (@hanzo/appearance, @hanzo/design), where every price and checkout link
  lives, scripts, and known differences from live
- docs/build-notes/: status files, request notes, per-page checklists and reviews, plans
- Removed: screenshot galleries, captures of third-party sites used as references,
  the generated status page and its script, editor config, a personal working-rules file
- Code comments point at the new docs paths (no code changes)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
2026-11-08 13:22:36 +00:00

12 KiB
Raw Permalink Blame History

/crawl — James-eye review

Ready: 2026-11-08 copycheck missing 0 of 63 (COPY-RULE): "api /v1/crawl" restored as one plain line in the close (SafeClose: api line and repo name each one text element, as on hanzo.ai); no images on live or ours; usability: Read the docs, GitHub, plans, console, agent prompt all present; taste OK, unique OK, check.mjs 0 errors/0 overlaps/no h-scroll at 1470 and 375, reduced motion 0 animations and 0 errors.

Verdict: 7.5/10 First complaint: "The stepping scene is great, then it turns into a document again. 'How it works' is fetch, extract, render all over again as rows of text with little grey stamps, nothing moves, and there's a big empty white gap before and after it. And on my phone the same paragraph shows up twice."

Walked 7 Nov 2026 on the dev server at 1470×801 and 375×812, moving. Method: Playwright with a recorded video, wheel notches of 130px (6 per screen) with 1.2 s dwell, frames every 300 ms for the first 1.8 s, hover then click on every control in main, a press probe, a 12-stop Tab crawl and Esc, a reduced-motion pass, phone screens every 0.85 screen with taps on the stage and tab buttons, cookie card dismissed with Reject all, and 9 extra cold loads to chase the console error. Proof: docs/build-notes/review/crawl/desktop-sheet.jpg and docs/build-notes/review/crawl/phone-sheet.jpg, both new this round. diagram-overlap.jpg and desktop-walk.jpg in that folder are older and not part of this review.

What works

  • Alive at once. At 0 s the POST /v1/crawl bar is already typing (https://example.com/doc). By 1.5 s the black Markdown panel streams # API / ## Authentication / - [Keys](/docs/api/auth). The path tabs (/docs/api, /blog/launch, /pricing/faq) cycle on their own, and the 44px pause button really pauses (the icon flips to play and the stream stops). This is the product doing its job as the hero.
  • The pinned "Three steps, and a boundary" stage is a real signature. The section is 5,072px tall and pins a #f5f5f5 stage. Six progress hairlines fill with scroll, and the chapter list steps from #737373 to ink. Each chapter swaps in its own object: the page wireframe with the content box lifted out; fetch + parse beside a black Headless Chromium column; the site tree with 169.254.169.254 refused; 302 refused at the hop; then the HTTP and MCP cards joined by a dot line. One thing comes in as one goes out. It is the Apple pinned-scene idea done properly.
  • The pricing selector answers. Clicking Unlimited changes the figure (about 64px Air) from 50,000 to Unlimited pages. The line under it becomes "Enterprise · Custom · Unlimited concurrent crawlers", the track fills, and the Enterprise column takes the ink outline.
  • Press and hover are mostly right. The solid ask presses at scale(0.98) and darkens on hover (#0a0a0a to #2c2c2e). The "GitHub →" arrow now slides 4px. The outlined plan asks gain an inset fill and a darker border. The chapter rows go from grey to ink. The Related rows fill #ededed.
  • Fixed since last round: the RETURNS words are now 32px, not a wall of 64px. Copy is 74×44.
  • Clean: a computed-colour scan of main found 0 chromatic values. Only Zen and Zen Mono are used (Noto Kufi sits first in the stack for Arabic only). CLS was 0.0004 across the full scroll. The h1 box holds at x159 y335, 659×53. There is no horizontal scroll at 375 (scrollWidth 375). The focus ring is a 2px ink outline on every Tab stop.
  • The phone is its own composition. The h1 is 40px. The h1, lede and solid ask end at y234, well above the fold at 375×667. The stage becomes a card with a pause button and 01 to 06 chips (44px). The plan cards stack one per screen.
  • Different from its neighbours. /search has a centred hero over a search-box demo, and /bot has a left headline beside a chat roster. /crawl has a bottom-aligned split (h1 left, lede and asks right) over a browser-to-Markdown demo, plus its own site-tree stage.

The 11 answers

  1. Sells in 5 s, moves in 1 s? Yes. "Hanzo Crawl / Give it a URL, get back Markdown", the solid "Read the docs", and the URL typing in the very first frame. One small thing: the lede settles from y254 to y250 while the asks and meta line arrive, so the right column nudges up about 4px.
  2. One in, one out, or a document? It is one-in-one-out for the first 6,300px (the hero demo and the pinned stage). Then "How it works" (section.kfs, 1,425px) is a ruled spec sheet: STEP 01 to 03, TWO WAYS TO CALL IT, READS, RETURNS. It has 0 running animations when scrolled into view (measured after 2.5 s), and it retells fetch, extract, render straight after the stage told it. The pricing, "Send it a URL" and Related stretch reads calmly, but that block is a document.
  3. A real visual in every section? Mostly. Hero: the live crawl demo. Stage: six objects. How it works: thumbnails of about 215×130 only (a dial, a wireframe, a Markdown tile). They are too small and too static to be the section's object. Pricing: the selector card plus the plan sheet. "Send it a URL": the Hanzo console mock. It loops "deploy the gateway to staging / reading the project", which is frozen live copy but says nothing about crawling. Band: the agent-prompt block.
  4. One ask, nothing floating; scale rhythm? On desktop the header ask flips to a solid "Read the docs" once the hero ask leaves view, and nothing from the page floats over content. But "Read the docs" appears 4 times in main: the hero (solid), the Build and Scale plans (outlined), and "Send it a URL" (outlined). The band adds "Deploy to Cloud" as a solid white fill. That is over MASTER's 3-appearance cap. Scale rhythm: h1 52px, h2s 26px, one 64px figure on the pricing screen, body 14 to 16px, and the band head at 44px. That is good now that RETURNS is 32px.
  5. Every hover and press answers? Nearly. Two things look like controls but do nothing. The six READS chips (li, #f5f5f5, radius 8px, about 44px tall) and the HTTP /v1/crawl and MCP pills both read as buttons. "View on GitHub →" in "Send it a URL" showed no colour, background or underline change on hover (I did not separately probe its arrow). There are no layout jumps: every hovered width was identical before and after.
  6. Overlap, font swap, layout shift? No overlap at either size, no font swap, and CLS of 0.0004. On the phone, though, the first chapter's content renders twice. "The readable part, not the page" plus its paragraph sit at y1329/1390, above the stage. Then the same h3 text and the same paragraph ("Deciding which subtree is the article…") appear again under the stage chips at y2025/2057. Both copies are visible within about 700px of each other (m-01, m-02 on the phone sheet). On desktop, mid-scroll as the hero card narrows, the black Markdown panel goes empty while the next path restarts (d-s00). That reads as a blank slab for a moment.
  7. Which reference, and is its motion there? apple.com product page: the product as the hero and a pinned stage with one panel changing. Yes, that is genuinely there. motion.dev-style state changes (the tab pill, the plan selector) are there too. Pointer motion is still missing: no tilt, no cursor-aware light, no magnetic ask. The mix is idle, time, state and scroll, with nothing for the pointer.
  8. Different from neighbours? Yes in hero layout and in the stage, as listed above. The shared formula still shows underneath: the same "Read the docs + GitHub →" pair over a wide framed demo with a pause button, as on /search.
  9. All 18 parts? Visibly covered: one h1, one main, the sticky ask, the live demo with a pause control first, a real plan selector, copy that equals the display, plan cards as one sheet, a phone composition, focus rings, and no hue. Weak: part 3 (How it works breaks one-in-one-out, and there are 323px dead gaps: the hero object ends at y1069 and the "Three steps" h2 starts at y1392); part 4 (the primary appears 4 times, plus the band's different solid); part 8 (the READS and HTTP/MCP pills are styled like controls but inert); part 11 (the duplicated chapter text on the phone, and "View on GitHub" is a 127×21 tap target on the phone). Reduced motion: the page shows its final state (the 302 stage is complete in rm-mid). But getAnimations() still lists 5 entry animations after 3.5 s (knl-up, kns-in ×3, kns-rise), where MASTER asks for an empty list.
  10. Banned tells? None found. No hue, gradient, Inter, glow or serif italic. No pill above a heading: "AI-READY WEB CRAWLER" sits under the asks, and "FETCH, EXTRACT, RENDER" sits under "How it works". "RELATED CAPABILITIES" heads a list, not a heading.
  11. Copy untouched? Every Hanzo line I read on screen matches content/live/crawl.json, including the console prompt "deploy the gateway to staging". On the phone the hero tabs shorten to /api, /launch, /faq. These are demo labels, but they are not the live paths shown on desktop, so show the full paths or confirm they are not copy.

Fix list (to reach 8+), most important first

  1. Phone: remove the duplicated chapter text in .cr-sc. The h3 and paragraph for the active chapter show above the stage (y1329) and again under the chips (y2025). Keep one copy: the one under the chips, which follows the tapped chip, is the right one.
  2. Make "How it works" (section.kfs) a moment, not a spec sheet. It has 0 running animations in view and retells the stage. Give it one object at stage size that the STEP rows drive on hover or focus (the guarded dial, then the extracted subtree, then the Markdown render), or play the three thumbnails once through on entry. Keep every word.
  3. Close the 323px dead gaps between the hero object (bottom y1069) and "Three steps" (y1392), and around How it works and the pricing note. At 801px that is 40% of a screen of white. Overlap the outgoing and incoming objects by about 40px, as MASTER part 3 asks.
  4. Cut "Read the docs" to 3 appearances. Drop the plan-card repeats to text links, or let "Send it a URL" carry the label as text. The labels stay; only the weight and count change.
  5. De-button the inert pills. The READS chips and the HTTP /v1/crawl / MCP pills should read as text tags (no 44px pill fill), or do something when pressed.
  6. Hover for "View on GitHub →" in "Send it a URL", to match the hero GitHub link's 4px arrow. On the phone, give it a 44px tall hit area (it is 127×21 now).
  7. Don't blank the Markdown panel mid-scroll: keep the last streamed output until the next one starts writing.
  8. Reduced motion: let the entry animations finish and clear. knl-up, kns-in and kns-rise are still in getAnimations() after 3.5 s; MASTER wants an empty list by 3 s.
  9. Add one pointer moment on fine pointers (a slight tilt or a cursor-aware sheen on the pinned stage card), so the motion mix is not idle, time, state and scroll only.
  10. Phone hero tabs: show /docs/api, /blog/launch, /pricing/faq as on desktop (scroll the tab rail if needed), not /api, /launch, /faq.

Shared chrome

  • Intermittent console error: a React hydration mismatch ("A tree hydrated but some attributes of the server rendered HTML didn't match…") fired on the recorded walk, and the red "1 Issue" badge sits bottom left in every frame of that walk. It did not repeat in 8 further cold loads. An older review traced it to FooterHTML (data-x-shell="footer"). I could not reproduce it to confirm the source, but it blocks DONE item 3 whenever it fires.
  • Phone header: it stays a solid black "Try Hanzo" all the way down. With the hero's solid "Read the docs", the first phone screen has two solid fills, and the header never takes the page's label. On desktop it does swap to a solid "Read the docs" once the hero ask leaves view.
  • Cookie card at 1470: it sits centre-bottom over the hero demo until dismissed. "Reject all" has equal weight with "Accept all". Fine.
  • Footer on the phone is a fully expanded two-column link wall, not <details> groups as MASTER part 2 asks.