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

6.6 KiB

/datastore — James-eye review

Ready: 2026-11-08 copycheck missing 0 of 56 (COPY-RULE): hero query runs as hanzo.ai does (its four example queries in its order, all four in the page text, 3.2 s each, press a column for SELECT FROM events, resting "Reads 1 of 12 columns"); the twelve industries are plain text again (own element per row, scan visual kept beside them) and "api /v1/provisioning/datastore" restored; no images on live or ours; usability: Try Hanzo, Documentation, Self-host, ports, agent prompt; taste OK, unique OK, check.mjs 0 errors/0 overlaps/no h-scroll at 1470 and 375, reduced motion 0 animations and 0 errors. 7 Nov. Walked moving at 1470x801 and 375x812 (phone: isMobile, hasTouch) with Playwright on this worktree's dev server (:4182). At each size: frames at 0, 1 and 3 s with no input, then wheel scrolls of 0.85 of a screen with a 1.5 s dwell to the footer, hover and press on every control in main on desktop, taps on phone (a column in the hero console). Measured CLS, horizontal overflow and console output. Component: components/pages/cloud/Datastore.jsx.

Verdict: 7/10

First complaint: "It's clever, the columns lighting up and the table coming apart. But it's two long pinned bits back to back, six facts and then four more steps, and by the end I'm just scrolling through diagrams. Then there's a list of twelve industries with nothing to look at. And the console in the hero is half under the fold on my laptop."

The 11 answers

  1. Sells in 5 s, moves within 1 s: yes, with the object cropped. "A column store for analytical SQL" cuts in on the left; the lede, an outlined Try Hanzo, Documentation and a pause button are on the right. The events console scans by itself: the query rewrites (SELECT count()… at 1 s, SELECT country, count()… GROUP BY country at 3 s) and "Reads 1 → 2 of 12 columns" changes as the column files light up. At 1470x801 the console's column row starts at y≈750, so the thing that explains it (columns lighting) is mostly under the fold. On phone the console with its query and first row of columns fits under the lede.
  2. One in, one out: yes, but too much of it in a row. "What it does" pins six facts, each with its own diagram (column stack with codecs, three nodes, Raft quorum, local NVMe/object storage, events/metrics/logs partitioned by time, the ports table). "Where the speed comes from" then pins the exploded table through four states (column files, one instruction, sorted parts, compression). Both are genuine one-in-one-out stages, but they run back to back for roughly ten screens, so the middle feels long. On phone the exploded table plays its four states by itself or by tap, and the page is about 12,900px tall.
  3. A real object in every section: all but one. Hero console, six fact diagrams, the exploded table, the port board and the dark close all hold objects. "What people point it at" is a numbered two-column list of twelve industries with no visual.
  4. One ask, nothing floating: the ask is not solid on the first screen. The hero Try Hanzo is outlined (hover raises it with a border and shadow) and the header's Try Hanzo is outlined at the top, so the first screen has no solid fill; the header goes solid after scrolling. The close has Deploy to Cloud (solid) and Self-host (link). Nothing floats over content apart from shared chrome. Scale: 52px h1, 26px heads, and the port board's digits are the one figure moment. The exploded table grows and splits, which is the page's best scale change.
  5. Hover and press: yes. Every column in the hero answers hover with colour and border, and pressing one adds it to the query ("Reads 3 of 12", the SQL rewrites to GROUP BY country, plan); the tap does the same on phone, in view. The fact rail numbers and the protocol pills (HTTP, Native, MySQL, PostgreSQL) answer hover and press at scale(.97/.96), and picking a protocol settles the port onto the board digit by digit. Copy answers with a shadow and scale(.92). Weak spots: Documentation and Self-host only nudge 1px on press with no hover change on the link itself; the active column/pill shows no hover.
  6. Overlap, font swap, layout shift: one small shift on phone. CLS 0.0008 on desktop but 0.026 on phone (still under 0.1, but the only page of the three with a visible shift). No font swap; the h1 holds its box. No horizontal overflow. On phone "duration_ms" wraps to "duration / _ms" inside its column cell, both in the hero and in the exploded table.
  7. Reference: apple.com product page. Pinned scrubbed scenes with the product (the table) as the hero are genuinely there. The port board is a nice time-based detail. There is no huge-type moment and no synchronized-style card open.
  8. Different from its neighbours: yes in idea, no in frame. The exploded table and the port board are its own. The skeleton (KeynoteStage split, pinned chapters, KeynoteClose) is the same one /dashboards, /metrics and /o11y use.
  9. The 18 parts: card is 18/18 (docs/build-notes/coverage/datastore.md, every Done here: filled). On the page: one h1, a pause control, pressable columns, a rail, a radiogroup, Copy with a status and a closing band. Gaps: the industries list without an object, and the cropped hero object at 1470x801.
  10. Banned tells: none. Deck greys only (the column swatches are the neutral ramp), no Inter, no gradient. "HANZO DATASTORE" sits below the asks, beside the pause button, not above the h1. scripts/taste.py: OK.
  11. Copy: untouched. scripts/parity.py /datastore: OK, text 78/78, links 5/5.

Not counted: a red "1 Issue" hydration badge in walk contexts, clean on a fresh single load (shared finding 3). scripts/unique.py: no clash for /datastore.

Fixes, in order

  1. Shorten the middle. Two pinned runs back to back is too long. Either merge them (the six facts become the exploded table's states, so one table carries the whole story) or unpin "What it does" into a horizontal card rail, so only the exploded table pins.
  2. Give the industries an object. Let the twelve industries be what the hero console queries (each row a WHERE value that lights the console), or a quiet type wall that the scan passes over, instead of a numbered list.
  3. Lift the hero console into the first screen at 1470x801, so the column files and their light are visible without scrolling (raise the console or shorten the hero top padding).
  4. One solid ask on the first screen. Make the hero Try Hanzo solid (or the header's while the hero is in view).
  5. Phone: fix the phone layout shift (CLS 0.026) and the "duration_ms" wrap (smaller mono size or a wider cell for that column).
  6. Hover on links. Give Documentation and Self-host an underline draw or arrow nudge.