WORK-389
Setting up your dashboard 0 entities found · 9/32 branches scanned
ID:WORK-389Status:review

3D sitemap showcase

The launch showcase for the data-bound sandbox — and the simplest, since the data already exists: the core pageTree. A data-shape="tree" sandbox renders the site as a navigable 3D map (three.js tree/force layout); nodes link to their URLs.

Priority:mediumComplexity:moderateMilestone:v0.21.0Source:SPEC-093
claude/sitemap-star-systems View source

Criteria completion

Criteria completion: 3 of 4 (75%) checked; tracking started on Jun 11, no incremental history yet0%25%50%75%100%Jun 11Jun 15

Tracking started Jun 11 — check back for trends.

Relationships

Implements 1
Related 3
Branches 5
claude/sitemap-star-systems current review
changeset-release/main readyclaude/work-389-3d-sitemap reviewclaude/work-381-sandbox-lazy-activation donemain doneclaude/v0.21-work-breakdown ready
History 1
  1. 2319f71
    Created (review)by bjornolofandersson

Acceptance Criteria

  • A data-bound sandbox (data="type:page" data-shape="tree") renders the page tree as a 3D sitemap; nodes are clickable to their URLs.
  • An authored fallback renders the same tree as an honest collection (a real, navigable page tree) for no-JS / no-WebGL / screen readers.
  • Honours prefers-reduced-motion (static frame) and is lazily mounted (poster until in view).
  • Pinned three.js; vite build green (no SSR/WebGL at build).

Dependencies

  • WORK-388 (the data channel + tree shape) and WORK-381 (lazy/poster mount for the heavy WebGL).

References

  • SPEC-093 · core aggregate phase (pageTree)

Resolution

Completed: 2026-06-11

Branch: claude/work-389-3d-sitemap.

What was done

  • site/examples/sitemap-3d/index.html — a three.js scene that reads window.RF_DATA.tree and renders the pages as nested star systems: top-level sections sit on a golden-angle galaxy disc (a flat radial tree piled all 60 roots at the origin — this spreads them), each page orbits its parent as a little planetary system, nested by URL depth. Orbital motion (reduced-motion → frozen), a distant starfield, emissive glow + star twinkle, drag-to-rotate + gentle auto-spin, hover tooltips, and click-to-navigate (window.top.location → the node's URL). Space-dark in both themes, pinned [email protected], try/catch → the accessible fallback.
  • runes/sandbox.md gains a "Data binding — window.RF_DATA" section: documents data / data-shape / data-fields / data-limit, the live 3D sitemap of the rune section (data="type:page url:/runes/*" data-shape="tree"), and an authored {% collection %} fallback over the same query.
  • Bug fix (in WORK-388's data-resolve.ts, surfaced here): page urls have no trailing slash but parentUrls do, so toTree never nested. Added stripSlash normalization; the unit test now uses the real convention and asserts nesting.

Verification

  • Full sveltekit site build green; the sandbox emits data-rf-query/data-rf-shape=tree and the resolved data-rf-records payload nests correctly — 60 roots, 9 plugin sections with their rune children nested (50 children) — and the collection fallback renders. This doubles as the cross-adapter (sveltekit) confirmation of WORK-388's resolver.
  • data-resolve.test.ts green (8); runes build clean.

Why review, not done

  • The actual 3D render + click navigation needs a browser (window.RF_DATA reaching the iframe — the live test WORK-388 was waiting for). The data is verified end-to-end; the WebGL render isn't headlessly checkable. A glance at cd site && npm run dev → /runes/sandbox (the "Data binding" section) confirms it.
  • Lazy-mount deferred: criterion 3's "lazily mounted (poster until in view)" needs WORK-381 (not yet done). The scene is eager for now — consistent with sandbox.md's other live sandboxes; it'll lazy-mount once WORK-381 lands. (reduced-motion is done.)
  • The fallback is a flat navigable collection list (collection doesn't render nested trees) — the same data, accessible; a nested-tree fallback would need a new layout.