Repository navigation
✨ feat(showcase): a Home built on a live Glitch Lab monitor; ⌘K searches the site - #75
Merged
Merged
Conversation
JadRizk
force-pushed
the
claude/nexus-home-redesign-03de00
branch
from
October 9, 2026 10:00
d6d1bd5 to
89cd974
Compare
…hes the site Home was a three-panel console demo in a 760px box with no headline, no way in, fake sliders and a theme panel duplicating the header. It is now a hero, the routes into the site, and a plain footer. - Hero: the pitch (h1, lede, build-time figures in data-nx-figure spans, Get started / Browse components) beside a CRT running Glitch Lab's own shader pipeline and synthesiser. Each visit lands on a random channel (graph with a fresh layout, bars or HUD). The pointer tunes colour bleed and tracking; Jolt rotates scrub, interference and degauss (the faults that move the picture rather than flash it); Sound voices them, and the room noise fades up while the pointer or focus is on the monitor. The CRT bends, with an overscan so no black shows at the corners. Reduced motion: a still frame, no faults, no sound. Capped at 30 fps and 1x. - Five links (Get started, Tokens, Components, Graph, Glitch Lab) and a borderless footer. - Glitch Lab's engine and synthesiser are split out of GlitchLab.jsx into effects/glitchEngine.js and glitchAudio.js, shared with the hero. Seed 0 and overscan 0 reproduce Glitch Lab's own picture; the engine gains optional fps/dpr caps, a layout seed and a fade on the noise bed. - ⌘K / Ctrl+K and "/" open a site palette on every route (SitePalette.tsx): every page plus the theme and CRT actions, each kind with its own glyph. Theme and CRT left the header; Search is its only control. The palette stands aside on the CommandPalette page, which demonstrates its own. - <main> scrolls on Home, so it gets the route-change scroll/focus reset. Tests: crt-off, crt-on, console-hud-aa, console-hud and focus-skip-link re-recorded (the hero canvas is masked); the harness drives theme and CRT through the palette; the keyboard-reachability check now covers Home; routing.spec covers the palette; new home.spec.ts covers the monitor. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
JadRizk
force-pushed
the
claude/nexus-home-redesign-03de00
branch
from
October 9, 2026 11:30
7a9a177 to
3cbb97f
Compare
JadRizk
added a commit
that referenced
this pull request
Oct 10, 2026
…yboard and screen-reader navigation (#93) * 📝 docs(graph): migration spec, usability research and build brief for graph 2.0 The plan for merging qrntn's graph fork back into @nexus-cyberdeck/graph as its 2.0 engine: - graph-migration-qrntn.md: the two-way merge spec (fork base 84f8eca, qrntn at da0823b), decisions D1–D10, the nine-phase build order with notes on what each phase decided, and the test plan. - graph-usability-research.md: what makes an interactive graph usable (task taxonomy, degree-of-interest exploration, mental-map stability, accessible network navigation from QUARTZ / Zong et al. / Data Navigator), a scorecard of both graphs, and recommendations R1–R12. - graph-build-brief.html: a one-page brief with a working prototype of the keyboard navigation model. - graph-screen-reader-pass.md: the manual NVDA / JAWS / VoiceOver script and results table, a release gate for 2.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 💥 ✨ feat(graph)!: graph 2.0 — qrntn's renderer, Nexus's hardening, keyboard and screen-reader navigation Merges the graph qrntn forked on 2026-08-25 back into @nexus-cyberdeck/graph as its default engine. qrntn's version is the base, and every fix Nexus made after the fork is re-applied on top. Neither graph had accessible navigation, so that is new. Spec: docs/specs/graph-migration-qrntn.md. Engine - Pure modules pulled out of GraphCanvas, each tested: picking, labels, neighbourhood, validate, camera-rig, random. - Physics: sector and ring forces with a slower structural schedule, reseed(), per-node size/sectorAngle/radiusTarget overrides, and a seed that defaults to a hash of the node ids. With both forces at 0 the solver matches a recorded 1.x run float for float. - Camera: the intro tracks the settling layout; fitInset keeps framing clear of floating chrome; followSelection; focus() follows a node while the layout settles; under reduced motion every move lands at once. - Edges: straight / arc / etched routing, per-category gain, screen-pixel dashes, frayed absent ends, two-pass compositing, three hover tiers, and direction drawn by end pads (filled bar → open bracket) instead of arrowheads. - Props: invalidEdges + onWarning, selectionScopedLinkCategories, onFrame, drawnNodes, DEFAULT_PHYSICS / DEFAULT_OPTICS. - A click selects without grabbing, so selecting no longer reheats the layout. Accessibility - One Tab stop into a named role="group". Inside, ←→ browse connections, ↑↓ change direction, Enter follows, Backspace goes back, Space selects, D describes, ? helps, and Escape steps out. A polite live region speaks relation, node, kind and position. There's a canvas focus ring, the browsed edge is highlighted, a key hint shows, and the camera follows focus. - controller.back() / canGoBack share one history with the pointer, and focusNode() puts the reader on a node. - describeGraph() returns the graph as an outline, rendered by the new <GraphOutline> in @nexus-cyberdeck/react. - Reduced motion also stills edge jitter, packets, sync marks, the intro sweep and the selection pulse. Breaking: LinkCategory.arrow removed; dash is in screen pixels; default optics retuned; the root is role="group" (keyboardNavigation={false} keeps role="img"); the layout is the same on every visit by default (seed={null} for random); GraphStats.drawnNodes is required. See "Migrating from 1.x" in packages/graph/README.md. Showcase: seeded sample data, link kinds told apart by form, frayed links to unresolved questions, fitInset for the console and drawer, Back and "View as list" buttons, a drawer that stays non-modal for keyboard selections, and a GraphOutline page. Tests: browser/graph.spec.ts adds a WebGL compile check, seeded fake-clock baselines (rest, selected, keyboard), a measured edge contrast (resting 3.56:1, live about 17:1), a keyboard walkthrough and the list view. Graph unit tests go from 46 to 245. Not done: the manual screen-reader pass (docs/specs/graph-screen-reader-pass.md) gates the release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ✅ test(graph): follow main's palette-driven harness and refresh the baselines it moved - The frozen-clock graph test set the CRT layer through the header button that main's Home redesign (#75) moved into the ⌘K site palette. It now checks `data-nx-crt` and goes through the palette only if it needs to, as gotoPage does. - Regenerated the three graph baselines and the token reference's text roles, which now carry both main's changes and GraphOutline's entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🐛 fix(graph): pass the CI gates main added — ES2020 lib, docs claims, coverage Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🐛 fix(graph): review fixes — drawer modality, scoped cursor, hidden back steps, outline parity - showcase: a mouse click opens the drawer modal again (the root takes focus on click; only the graph's focus target means a keyboard selection), Back tracks keyboard history through onNavigate, and the list view honours isolate - navigator: back() and Home skip nodes a filter has since hidden; canGoBack agrees; a refilter keeps the browse cursor on the same edge, including the one a selection-scoped category triggers - canvas: "Moved to …" is only spoken while focus is in the graph; the neighbourhood walk no longer crosses hidden edges - describeGraph: generic over node data like GraphCanvas, and takes isolateId - GraphOutline: category ids are encoded into heading ids - camera: the intro sweep never starts past ZOOM_MAX Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🐛 fix(graph): second review — Escape exits cleanly, spoken counts match, selection source in onSelect - Escape: the focus target leaves the tab order while the root holds focus, so the next Tab moves past the graph instead of straight back in - the ariaLabel warning reads the literal process.env.NODE_ENV, so production bundles strip it - the connection count a node is described with (canvas and outline) is the reachable one, matching what browsing and the outline list - onSelect(node, source): "pointer" | "keyboard" | "controller"; the showcase drawer uses it instead of reading an internal data attribute - back() at the start of the path keeps hidden steps for when the filter lifts - GraphOutline: the selected node gets a note, not a pressed button that can't be released; focus moves to the entry when its button gives way - Button: aria-disabled looks disabled; the showcase Back button uses it so it keeps focus when it runs out of history Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🐛 fix(graph): third review — showcase Escape respects the graph's, migration guide gaps, toggle names - showcase: the page-wide Escape skips an Escape already handled, so leaving the graph or deselecting in it no longer throws away an isolation - showcase: "View as list" is an action, not a pressed toggle with a flipping name; the drawer's Isolate keeps one name while pressed - screen-reader pass: step 7 describes Escape as the code does it - migration guide and changesets: `curve` only bows `routing: "arc"`, and PhysicsConfig/PhysicsParams gained required sectorForce/radiusForce - random.ts: correct the reasoning on ids 1 and "1" Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🐛 fix(graph): fourth review — empty graph mounts, tooltip Escape is handled, npm description - an empty graph, or one mounted with everything filtered out, no longer crashes to SYSTEM HALT: the focus target is named for the graph, keys that need a node speak the summary, and a lifted filter lands on a node - the Escape that only dismisses a hover tooltip calls preventDefault, so a page-level Escape leaves the selection and isolation alone - package.json: describe 2.0, not 1.x's curved links Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🐛 fix(graph): a screen reader's activate command selects the focused node The focus target is a toggle button, but only listened for keydown. In browse mode a screen reader activates a button with a click (VO+Space, NVDA/JAWS Enter), which did nothing. A click now toggles the selection, as Space does; real Enter and Space keydowns are preventDefault-ed, so nothing fires twice. README, onSelect's docs and the screen-reader pass say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ♻️ refactor(graph): one adjacency, one isolation rule, an allocation-free frame - the navigator's ranked connections are the only adjacency: the neighbourhood walk, tooltip, selection framing and getNode() read them (NavConnection gains `out`); getNode() rows are unchanged, self-loops and tie order included - isolationSet() is the one isolation rule, shared by the canvas and describeGraph, so the outline can't drift from what is drawn - the focus target's name is rebuilt only when the node, its selection, visibility or describeNode change, not on every hover - onFrame gets one geometry object, refilled every frame - mulberry32 and seedFromIds are exported; the showcase uses them instead of a copy No behaviour change: unit suites pass and the browser baselines are untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 📝 docs(graph): say onFrame reuses its whole geometry object, not just the arrays Since the frame loop stopped allocating, onFrame hands over the same object and camera every frame. The docs only said the arrays were reused, which left keeping the object (in React state, say) looking safe; it never re-renders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🚨 chore(lint): clear the code-style warnings in this PR's files main's new code-style rules (#95) flagged 69 warnings across the files this branch touches. All are fixed; packages/graph stays exempt, as main's config has it. - Showcase graph page: NexusCyberdeck.tsx (964 lines) split into the page, GraphConsole, GraphLegend, InspectorDrawer and OutlinePanel, with the slider defaults and tables in controls.ts and the taxonomy in taxonomy.ts. Category lookups go through nodeCategory()/linkCategory() instead of `!`. Booleans renamed to isListView, isKeyboardSelection, isRunning. - sampleData.ts: the generator is split into small steps that draw from the one random stream in the same order; its output hashes the same at four sizes and two seeds, so no baseline moves. - a11y.spec.ts, already over 300 lines on main, split along its own two halves: axe scans stay, the direct claims move to a11y-claims.spec.ts. test:a11y and the README name both. - Test `!`s replaced with assert() or dropped where the type is non-null; GraphOutline's `selected` local is `isSelected`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🎨 style(react): trim GraphOutline comments to the constraints and spell out its locals Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ♻️ refactor(showcase): bring the graph page in line with the code style Full names for cfg, ev, k/v and friends (DEFAULT_CFG is DEFAULT_CONFIG, the console's cfg prop is config), handleX for local handlers, and `as const satisfies` on the taxonomy and slider tables, which now export NodeCategoryId and LinkCategoryId. Comments are cut to the one-line whys. sampleData still draws from `random` in the same order. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🎨 style(graph): cut comments to JSDoc and one-line whys, spell out locals Drops the history, narratives and restated GLSL, keeps JSDoc on the public API for units, ranges, defaults and invariants, and renames abbreviated and one-letter locals (cfg, idx, pos, ev, c, f, p, w, ...). The ref mirrors in GraphCanvas stay, with a note that useEffectEvent needs React 19. No exported names, announced text, arithmetic or draw order change; the contrast test now reads the tooltip span by its new name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🎨 style(graph): trim test and browser-spec comments, spell out locals Assertions, titles, expected values and screenshot names are unchanged; the comments main already had in a11y-claims.spec.ts stay. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * 🔧 chore(showcase): start the graph page with a 60-node corpus The corpus-size slider's minimum is now its default. The graph baselines, the browser tests' node counts and the screen-reader script's example announcements follow the smaller sample graph. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.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
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.
What changed and why
Home was a three-panel console demo in a 760px box: no headline, no way in, fake Solver sliders, an unexplained "60", and a theme panel duplicating the header. It is now a hero, the routes into the site, and a plain footer, written for an evaluator first.
Hero. The pitch on the left (h1, lede, build-time figures in
data-nx-figurespans, Get started / Browse components). On the right, a CRT running Glitch Lab's own shader pipeline and synthesiser:overscanknob scales the bent picture out so no black shows at the corners.Below: five links (Get started, Tokens, Components, Graph, Glitch Lab) and a borderless footer.
Glitch Lab, split. Its shaders, events, presets and render loop moved to
effects/glitchEngine.js, and its synthesiser toeffects/glitchAudio.js, so Home and Glitch Lab share one copy.uSeed = 0andoverscan = 0reproduce Glitch Lab's own picture; Glitch Lab's tests still pass and it renders as before. The engine gains optional fps/dpr caps, a graph-layout seed and a fade on the noise bed.⌘K searches the site. ⌘K / Ctrl+K and
/open one palette on every route: every page, plus Switch theme and Turn CRT on/off, each kind with its own glyph silhouette. Theme and CRT left the header; the header's Search button is the visible way in. On the CommandPalette docs page the site palette stands aside so that page's own demo keeps the shortcuts.<main>now scrolls on Home, so it gets the route-change scroll and focus reset. Site-chrome CSS is inshowcase.css, semantic tokens only.Baselines that changed, and why
Five, all reviewed as diff images before re-recording. The hero canvas is masked (it runs on the frame clock, so no two captures agree); the frame, controls and everything else are compared.
crt-off.png,crt-on.png,console-hud-aa.png,console-hud.pngfocus-skip-link.pngTests
graph/NexusCyberdeck.tsx), unit tests in all workspaces, and the full browser suite (208 passed, including axe on Home in both themes).harness.tsdrives theme and CRT through the palette (runSiteAction) and exportshomeMask.a11y.spec.ts: the keyboard-reachability check looped overDOC_ROUTESonly and never covered Home; it does now.routing.spec.ts: three palette tests (go to a page, run an action, stand aside).home.spec.ts: random channel and graph on load (14 reloads), Jolt rotation and the single-fault rule, the room noise on hover and focus, and reduced motion. The animated cases aretest.slow(): they wait out real faults on a software WebGL renderer.Chose not to do
--nx-z-draweris0, so a Drawer mounted before positioned page content paints under it. It broke the earlier Home console; Home no longer mounts a Drawer, so nothing in the showcase shows it now. A library fix, tracked separately.--nx-font-stencilstarts with Impact, which the Linux Playwright container lacks, so the h1 shows in the fallback sans there (the Wordmark already did). Pre-existing.🤖 Generated with Claude Code