Files

9.6 KiB
Raw Permalink Blame History

/functions — James-eye review

Ready: 8 Nov, held up next to /api and /agents (no score). Wireframe filler replaced with real state (GPU nodes hold filled and hollow pods, versions carry pods and a two-part traffic bar that moves with canary or Blue/green), trigger curves reach handler.js, phone chapters run top to bottom, use cases became an uneven grid of live tiles that each grow into their sheet, hero triggers fire a fresh run on click and the first frame shows filled slots, the cluster swells as it fills and settles, no lifted runtime tile, no doubled sentences, 320 fixes. taste/unique/parity OK (text 79/79, links 7/7); 0 console errors, no overflow/overlap at 1470x801, 375x812 and 320. 8 Nov copy rule: copycheck missing 0 of 52 (Hanzo's words now sit whole in their own elements, nothing reworded). 7 Nov, round 4. Walked in Playwright Chromium at 1470x801, 375x812 and 320x812 (phones with isMobile and hasTouch). At each size: frames at 0, 1 and 3 s; wheel-scrolled one screen at a time with a 1.5 s dwell; hovered, pressed and tapped the triggers, runtime tiles, chapter steppers, GPU toggle, canary/Blue-green radio, use-case rows and sheet (closed with Esc and with Back), Copy and related links. Also loaded with prefers-reduced-motion at 1470 and 375. Screenshots use caret 'initial' and the cookie card was dismissed.

Verdict: 7/10

First complaint: "It's neat, but half of it looks like a wireframe. Grey placeholder bars, empty dashed boxes and lines that don't reach the box they point at. Then the same numbered list with a changing panel comes twice in a row. And on my phone five of the six chapters slide off sideways, so I scroll straight past them."

The 11 answers

  1. Sells in 5 s, moves in 1 s? Yes. The h1 and lede are Hanzo's own. The handler.js code types itself from 0 s and is complete by 3 s. The demo then fires a trigger by itself: the chip goes ink, pods fill and "Scale to zero" is struck through. The weak spot is that the hero is a grey rounded box holding a smaller white box. At 3 s nothing has fired yet: the pods are empty outlines and no trigger is lit.
  2. One in, one out? Mostly. On desktop a pinned six-chapter stage swaps one panel per chapter, with a filling progress rule and a counter, and the use cases pin and swap as well. The problem is that these are the same move twice in a row: a numbered list and a changing panel (01–06), then again (01–04). On phones the six chapters become a sideways carousel inside normal vertical flow. One vertical swipe passes all six, and five are only reachable sideways, with a 12px peek as the only hint. Dead air of about 300px sits between the stage and the use cases, and again before the black room.
  3. A real visual in every section? Yes, but thin. Everything is home-made monochrome schematic. Chapter 4 (GPU) and chapter 6 (Versions) are filled with skeleton bars and empty dashed slots, which is the "lazy" look. In chapter 5 the two outer trigger curves stop about 33px above handler.js and never connect. This was seen at every frame and also under reduced motion. Chapter 2's pool is a row of empty outlines. The page has no real Hanzo media or product UI, while its neighbour /cloud/containers has a black console hero.
  4. One ask, nothing floating, scale rhythm? Pass. The header's "Try Hanzo" is the sticky ask, and the page's own pair is one solid button plus a text link. Nothing floats over content. Scale goes h1 52, h2 26, chapter h3 about 26 and figures 64, with mono labels small. Never is everything big at once. But nothing ever grows or shrinks as the moment, so it is calm rather than alive.
  5. Every hover and press answers, no jumps? Mostly. Hovering "Try Hanzo" runs the hero demo, which tells you something. Stepper hover shows the chapter name. Use-case rows slide their label, the GPU toggle moves the pod into the GPU node, and canary/Blue-green swaps the ink card. Sheet open, Esc and Back all work, and the URL is kept. Faults: the selected runtime tile lifts 6px and leaves the 2x2 grid ragged (Python sits higher than Go). Clicking a hero trigger (Kafka) only inks the chip; pods and handler do not react within 0.7 s. The "Try Hanzo" hover goes from ink to a lighter grey, which reads as a fade.
  6. Overlap, font swap, layout shift? Desktop clean, phones not. The h1 box is fixed (271px, 52px, same at 0, 1 and 3 s) and CLS is 0.0004 at desktop and 0 on phones. No horizontal page scroll. No hydration diff from this page at any size or under reduced motion. The only console errors are a parse error in components/pages/cloud/Guard.jsx, which is another chat's page and not counted. Faults on phones:
    • At 320 the "cron schedule" and "RabbitMQ queue" chips run out of the grey hero panel's right edge.
    • At 320 the chain "handler.js — HTTP route —" breaks, leaving a dangling dash with "Kubernetes" on its own line.
    • At 320 a vertical wheel over the agent-prompt <pre> is swallowed (overscroll-behavior: contain on a scroller that only scrolls sideways). The page stuck at scrollY 5520 of 8391 through 26 more wheel turns. This did not happen at 375 or 1470.
    • At 375 the hero code wraps mid-statement ("res) {", "req.json();").
    • At 375 the runtime tiles break "handler / file" onto two lines.
    • At 375 the GPU pod is larger than its dashed slot.
    • At 375 and 320 the previous carousel card's text shows cut at the left edge beside the current card.
  7. Which reference, and is its motion there? apple.com: a pinned stage where one panel changes, with a sub-step rail. That motion is there on desktop and gone on phone. synchronized.studio: the use-case arrow opens a full sheet, but it does not grow from the card; it simply appears. motion.dev patterns are present (state changes, typing). The chatgpt-enterprise kind of calm proof is missing.
  8. Different from neighbours? Partly. The hero medium (typing handler plus pod grid) is its own, unlike Containers' console and Machines' API panel. The six-chapter pinned stage with a 01/06 counter, though, is the same skeleton Machines uses.
  9. All 18 parts covered? Mostly. Hero, narrative, proof (licence and GitHub chips), conversion (header ask, Deploy to Cloud, copyable agent prompt), related links, reduced motion, keyboard steppers with "Chapter N" labels, and states are all there. Weak parts: mobile (part 11, because of the carousel and 320 faults), media (part 10, no real media) and the motion variety on phones.
  10. Banned tells? No hue, gradient text, Inter, glow or eyebrow above an h1 or h2. "WHAT YOU GET" sits below its h2, which is allowed. Borderline: placeholder skeleton bars and empty dashed boxes read as the "lazy look", and the button hover lightens.
  11. Copy untouched? Yes. Every sentence traces to content/live/functions.json. The labels are fragments of Hanzo's own sentences: "TRIGGERS", "handler file", "the same handler", "Webhook", "Image", "A TRAFFIC DECISION RATHER THAN ANOTHER BUILD". Some are recapitalised. Several chapters print the same sentence twice: chapter 2 shows "Scale to zero is still the default when nothing is calling." in both the panel and the paragraph, and chapter 6 repeats its last clause as a caption. That repetition is clutter, not invention.

Fixes, in order

  1. Replace the wireframe filler in chapters 4 and 6 with real state. In chapter 4, the nodes show pods (filled and hollow) the way the hero grid does, not grey bars and empty dashed squares. In chapter 6, the two version cards and the traffic bar show a split that moves when canary or Blue/green is chosen, instead of skeleton lines. The bar at 375/320 currently renders as a grey slab with a black sliver at each end.
  2. Join the two outer trigger curves in chapter 5 to handler.js. They currently stop about 33px short, at every frame and under reduced motion.
  3. Phones: make the six chapters a vertical sequence (or a pinned stage with the stepper rail) so vertical scroll passes through each one. Drop the sideways carousel, where five of six chapters are only reachable sideways and neighbouring cards show cut text at the edge.
  4. Make the second stage a different move from the first. Use cases currently repeat "numbered list plus changing panel" straight after the 01–06 stage. Let the use-case card grow into its sheet (synchronized.studio) instead of the sheet appearing over it, and drop the pinned list treatment.
  5. Fixes at 320:
    • Wrap the hero trigger chips inside the panel padding, as one column or with smaller chips.
    • Keep "handler.js — HTTP route — Kubernetes" on one line (smaller chips) or stack it with vertical connectors.
    • Remove overscroll-behavior: contain from the agent-prompt <pre>, or stop it scrolling sideways, so it no longer traps vertical scroll.
  6. Stop the selected runtime tile lifting 6px out of the grid. Mark selection with ink fill alone, or lift every tile's hover equally.
  7. Make the hero triggers answer when clicked. Kafka, cron and RabbitMQ should each run the pod fill and handler pulse as the HTTP route does on hover. At first paint, show one finished run rather than empty outlines, so the 3 s frame sells.
  8. Make the primary button's hover darken or press (translateY 1px or scale 0.98) instead of lightening to grey.
  9. Remove the doubled sentences inside chapter panels: chapter 2's "Scale to zero…" line and chapter 6's caption repeating the paragraph. Leave the paragraph alone and make the panel show the idea instead of re-printing it.
  10. On phone, stop the hero code wrapping mid-statement: horizontal scroll inside the code card or a smaller mono size. Keep "handler file" on one line in the runtime tiles.
  11. Give the page one moment that grows and settles back, as the taste file asks. For example, the hero pod grid scales up as it scales from zero, then settles.