pure-3d

bynothingness

create a 3d website

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for pure-3d

1. Introduction

pure-3d is a website whose content is presented in three dimensions. The product intent is deliberately narrow and complete: a visitor arrives at the site and experiences content as an interactive 3D scene that they can view, orbit, and navigate through. The artefact is the 3D — there is no stated product category, catalogue, commerce flow, or editorial archive behind it. Success is a working, explorable 3D web experience.

The audience is the Visitor: an anonymous, first-time or returning person who opens the site expecting to be inside something volumetric, motion-led, and slightly futuristic. The emotional register is awe and play, not commerce. The site must feel like a place, not a page.

This document specifies the current delivery: one publicly reachable page, Landing, that renders a full-viewport real-time 3D scene with a glass-and-HUD overlay, plus the visual, motion, and technical constraints that make that experience coherent.

Page 1 of 22

2. System Overview

pure-3d is delivered as a single first-party, publicly accessible web page. The page is a full-bleed real-time WebGL scene; all interface chrome is an overlay floating above the canvas rather than a document column. There is no sign-in, no account, no stored user data, and no server-side product state — the experience is entirely client-rendered and stateless from the visitor's point of view.

Actors

  • Visitor (human, active) — the only accepted human actor. Arrives anonymously, views and interacts with the 3D content, and navigates through it.
  • Rendering runtime (non-persona system actor) — the browser's WebGL/Three.js runtime that draws and animates the scene, and the static host that serves the page assets. These execute work but are not product participants.

Accepted behaviour

  • Present content in 3D on a publicly reachable page.
  • Let the visitor orbit and navigate the 3D content with the cursor and with scroll.
  • Keep the visitor oriented with live HUD telemetry and section navigation.

Ownership

The Landing page is owned by the application and is anonymously reachable. No provider-owned or external destination carries accepted product behaviour. No identity, session, or permission layer is required, because no accepted journey creates durable actor-specific state, a commitment, an entitlement, or a value transfer that must remain bound to a particular person.

Page 2 of 22

Exclusions

  • No account creation, sign-in, profile, or permission model.
  • No commerce, checkout, payment, or order state.
  • No user-generated content, uploads, comments, or social features.
  • No admin, moderation, or back-office surface.
  • No content management system or editorial workflow.
  • No multi-page information architecture beyond the single Landing page.

2a. Product Interpretation and Delivery Boundary

The entire product is one page that behaves like a place. Everything the visitor can do — look around, orbit the subject, scrub the camera through the scene, read telemetry, jump to a section — happens inside that single continuous 3D viewport. There is no second screen to reach and nothing to sign into, so the delivery boundary is simply: open the URL, and you are inside the scene.

Because the experience is anonymous and stateless, there is no protected area and therefore no access boundary to reconcile. The page is public by design, and the only "state" that exists is transient view state (camera angle, zoom, scroll position) that lives in the browser for the duration of the visit and is not persisted or attributed to anyone.

Everything described in this document is current. No future-horizon capabilities have been accepted, and none are specified here.

Page 3 of 22

2b. Source Content Inventory

Not applicable. No reference directive in this project declares a content_source, so there is no verified factual inventory to preserve. All copy in the product is generated from the creative direction (wordmark, section labels, telemetry readouts, CTA label) and is not sourced from an external factual corpus.

2c. Page Content and Component Coverage

Page 4 of 22

Landing

The single page of pure-3d. A full-viewport real-time 3D scene with a glass-and-HUD overlay. Anonymous access; no identity required.

Information and state

  • The current camera state of the 3D scene: azimuth (θ), polar angle (φ), and zoom/distance.
  • The current scroll position, which maps to a keyframed camera move through the scene.
  • Live render telemetry: frame time, node count, and camera coordinates.
  • The current section index, derived from scroll position and mirrored in the top bar and the telemetry rail.
  • Pointer position relative to the viewport centre, used to drive the parallax orbit response.

Primary actions

  • Orbit the subject — move the pointer across the viewport to yaw and pitch the 3D subject toward the cursor.
  • Drag to orbit — press and drag to rotate the camera around the subject directly.
  • Scroll to travel — scroll the page to scrub the camera through the keyframed section moves.
  • Enter the scene — activate the glass pill CTA to move the camera from the hero framing into the first content section.
  • Jump to a section — activate one of the three uppercase section links in the top bar to move the camera to that section's keyframe.

Supporting actions

Page 5 of 22
  • Read the telemetry rail for live camera and performance values.
  • Read the orbit-ring angle readout to confirm the current azimuth.
  • Hover a glass panel to raise its border luminance and lift it 4px.

Domain entities

  • Scene — the single crafted 3D subject (an abstract crystalline torus-knot in iridescent glass) plus its supporting procedural layers: particle field, thin luminous wireframes, data streams, and a faint starfield/dust layer at 8% opacity.
  • Camera — the viewer's position and orientation in the scene, driven by pointer parallax, drag, and scroll.
  • Section — one of the keyframed camera stops below the fold (orbit → dolly-in → top-down), each paired with a full-bleed dark band and an asymmetric text block.
  • Telemetry reading — a live monospace value (θ, φ, zoom, frame time, node count).

Component responsibilities

Page 6 of 22
  • Hero canvas — full-viewport Three.js scene; renders the torus-knot subject, volumetric cyan rim light, magenta inner glow, bloom pass, and the dust layer. Owns the 40-second idle orbit loop and the cursor parallax response.
  • Split headline — the oversized PURE 3D display type, set in two lines with the second line indented two columns, anchored to the left edge and overlapping the object's silhouette so the geometry passes behind the counters of one letter.
  • Orbit ring — a 1px cyan ring circling the subject at a 15° tilt, with tick marks that redraw to match the current angle and a small monospace readout (θ 042.7°).
  • Top bar — fixed overlay: wordmark left, three uppercase section links centre, Drag to orbit micro-label right.
  • Telemetry rail — fixed left-edge column of JetBrains Mono readouts (camera θ/φ, zoom, frame time, node count) that updates live and doubles as the page's navigation index.
  • Glass pill CTA — bottom-left Enter the scene control with a cyan border and a magenta hover fill.
  • Telemetry block — bottom-right three-line monospace readout.
  • Section bands — full-bleed dark bands below the fold, each with a smaller inset canvas showing the 3D object beside a five-column text block, laid out asymmetrically rather than centred.
  • Light sweep layer — a horizontal light sweep that crosses the object every 8 seconds and marks section transitions.

States

Page 7 of 22
  • Loading — the scene initialises; the void background (#05060A) is painted immediately, the headline and overlay chrome render, and the 3D subject fades in as its geometry and materials become ready. A monospace initialising readout occupies the telemetry rail until live values are available.
  • Empty — not applicable; the page always has content to render and no collection can be empty.
  • Success — the subject is visible and lit, the idle orbit loop is running, pointer parallax responds within 400ms, scroll scrubs the camera between section keyframes, and telemetry values update live.
  • Error — WebGL unavailable or context lost — the canvas cannot render. The page keeps the void background, the headline, the section text, and the telemetry rail, and replaces the canvas with a static fallback frame of the subject plus a monospace notice that the 3D scene could not start. All section text remains readable and scrollable.
  • Error — reduced motion or low performance — when the visitor's system requests reduced motion, the idle orbit loop, light sweeps, and border pulse stop and the scene holds a composed static frame; the visitor can still drag to orbit and scroll to travel. If frame time degrades, the bloom pass and dust layer are dropped before the subject itself.
  • Recovery — a lost WebGL context is re-requested automatically; if it cannot be restored, the static fallback frame remains and the visitor can continue reading the page. Reduced-motion and performance downgrades are non-destructive and reversible on reload.
Page 8 of 22

3. Functional Requirements

FR-1 — Present content in 3D As a Visitor, I should see the site's content presented as a real-time 3D scene, so that the experience itself is three-dimensional rather than a flat page.

  • Provenance: explicit
  • Trigger: the visitor opens the site URL.
  • Observable result: a full-viewport WebGL canvas renders a single crafted 3D subject — an abstract crystalline torus-knot in iridescent glass with volumetric cyan rim light and magenta inner glow — over a near-black void background, with a bloom pass and a faint dust layer behind it.
  • Access state: anonymous; no identity required.
  • Failure/recovery: if WebGL is unavailable or the context is lost, a static fallback frame of the subject is shown with a monospace notice, and the page's text content remains readable.
  • Continuation: the visitor can orbit, drag, and scroll within the scene.
Page 9 of 22

FR-2 — Orbit the subject with the cursor As a Visitor, I should be able to orbit the 3D subject with my cursor, so that I can inspect it from any angle.

  • Provenance: explicit
  • Trigger: the visitor moves the pointer across the viewport, or presses and drags.
  • Observable result: the subject yaws up to ±6° and pitches up to ±4° toward the pointer with a 400ms ease-out; a direct drag rotates the camera around the subject. The cyan orbit ring redraws its tick marks to match the current angle and its monospace readout updates.
  • Access state: anonymous.
  • Failure/recovery: if the pointer leaves the viewport, the subject eases back to its idle orientation; if the canvas is unavailable, the static fallback frame is shown and no orbit is offered.
  • Continuation: the visitor can continue orbiting or scroll to travel to a section.
Page 10 of 22

FR-3 — Navigate the scene by scrolling As a Visitor, I should be able to scroll to move through the scene, so that the page reads as one continuous shot rather than stacked sections.

  • Provenance: explicit
  • Trigger: the visitor scrolls the page.
  • Observable result: scroll position scrubs a keyframed camera move — orbit, then dolly-in, then top-down — so each section below the fold is a camera keyframe rather than a fade. Section transitions are marked by horizontal light sweeps.
  • Access state: anonymous.
  • Failure/recovery: if the camera cannot be scrubbed (reduced motion or a degraded renderer), the sections remain reachable as ordinary scrollable content with their text intact.
  • Continuation: the visitor arrives at the next section and can keep scrolling or jump via the top bar.

FR-4 — Enter the scene from the hero As a Visitor, I should be able to start the experience deliberately, so that I choose when to leave the hero framing.

  • Provenance: explicit
  • Trigger: the visitor activates the bottom-left glass pill CTA labelled Enter the scene.
  • Observable result: the camera moves from the hero framing into the first content section, and the section index in the top bar and telemetry rail updates to that section.
  • Access state: anonymous.
  • Failure/recovery: if the camera move cannot run, the page scrolls to the first section instead so the visitor still reaches the content.
  • Continuation: the visitor is inside the first section and can scroll onward or jump to another section.
Page 11 of 22

FR-5 — Jump directly to a section As a Visitor, I should be able to jump to a named section, so that I can reach a part of the scene without scrubbing through it.

  • Provenance: explicit
  • Trigger: the visitor activates one of the three uppercase section links in the fixed top bar.
  • Observable result: the camera moves to that section's keyframe and the active link takes the magenta active-state underline.
  • Access state: anonymous.
  • Failure/recovery: if the camera move cannot run, the page scrolls to that section's band instead.
  • Continuation: the visitor reads the section and can jump to another or scroll onward.

FR-6 — Read live telemetry and stay oriented As a Visitor, I should see live readouts of the camera and render state, so that I understand where I am in the scene and that it is running.

  • Provenance: explicit
  • Trigger: the scene is running and the visitor moves, drags, or scrolls.
  • Observable result: the fixed left-edge rail shows JetBrains Mono readouts of camera θ and φ, zoom, frame time, and node count, updating live; the orbit ring shows the current angle; the bottom-right block shows a three-line monospace readout. The rail doubles as the page's navigation index.
  • Access state: anonymous.
  • Failure/recovery: before live values exist the rail shows an initialising readout; if the renderer is degraded or unavailable, the rail shows the last known or unavailable values rather than stale numbers presented as live.
  • Continuation: the visitor uses the rail to decide where to travel next.
Page 12 of 22

FR-7 — Read section content beside the 3D object As a Visitor, I should be able to read each section's content alongside the 3D object, so that the text and the geometry are experienced together.

  • Provenance: explicit
  • Trigger: the visitor scrolls or jumps into a section below the fold.
  • Observable result: a full-bleed dark band shows a smaller inset canvas of the 3D object beside a five-column text block, laid out asymmetrically rather than centred.
  • Access state: anonymous.
  • Failure/recovery: if the inset canvas cannot render, the text block remains fully readable at full width.
  • Continuation: the visitor scrolls to the next section.
Page 13 of 22

FR-8 — Respect reduced-motion and performance limits As a Visitor, I should have the experience adapt when my system requests reduced motion or the renderer struggles, so that the site stays usable.

  • Provenance: required_inference
  • Rationale: the accepted experience is continuous cinematic motion; a visitor whose system requests reduced motion, or whose device cannot sustain the frame budget, must still be able to view and navigate the accepted 3D content. This supplies only the prerequisite and fallback mechanics for FR-1 through FR-7 and introduces no new user goal.
  • Trigger: the operating system reports a reduced-motion preference, or measured frame time exceeds the budget.
  • Observable result: under reduced motion the idle orbit loop, light sweeps, and border pulse stop and the scene holds a composed static frame while drag-to-orbit and scroll-to-travel remain available; under performance pressure the bloom pass and dust layer are dropped before the subject itself.
  • Access state: anonymous.
  • Failure/recovery: downgrades are non-destructive and reversible on reload.
  • Continuation: the visitor continues to view and navigate the scene.

4. User Personas

Page 14 of 22

Visitor

Product context. The Visitor arrives at pure-3d anonymously, most likely from a link, with no prior relationship to the site and no account. They have not been told what the site is for, because the site does not have a stated product category — the 3D experience is the product. They arrive expecting to be inside something volumetric, motion-led, and slightly futuristic, and they judge the site within seconds on whether it actually feels like a place.

Primary goal. To experience the 3D website: to see content presented in three dimensions, to look around it, and to move through it. Success is a working, explorable 3D web experience — the scene renders, responds to them, and lets them travel through it.

Distinct accepted responsibilities. The Visitor is the sole human actor and carries every human-facing responsibility in the product:

  • Opening the site and receiving the 3D scene (FR-1).
  • Orbiting the subject with the cursor and by dragging (FR-2).
  • Scrolling to scrub the camera through the scene (FR-3).
  • Choosing to enter the scene from the hero via the CTA (FR-4).
  • Jumping directly to a named section from the top bar (FR-5).
  • Reading live telemetry to stay oriented (FR-6).
  • Reading section content beside the 3D object (FR-7).
  • Being served an adapted experience when their system requests reduced motion or their device struggles (FR-8).
Page 15 of 22

Relevant inputs and decisions. The Visitor's inputs are pointer movement, pointer drag, scroll, and activation of the CTA and section links. Their decisions are: whether to keep looking at the hero or enter the scene; which section to travel to; and how long to keep exploring. They make no commitments, submit no data, and create no durable state.

Interactions with other accepted participants. There are none. The Visitor is the only accepted human participant; no counterparty, recipient, or beneficiary is affected by anything the Visitor does. The rendering runtime and static host execute work on the Visitor's behalf but are non-persona system actors, not participants.

Observable success. The subject is visible and lit; the idle orbit loop runs; pointer parallax responds within 400ms; drag rotates the camera; scroll scrubs the camera between section keyframes; the telemetry rail updates live; and the visitor can reach every section and read its content. If the renderer fails, the visitor still sees the fallback frame and can still read the page.

Constraints carried from source. The Visitor is anonymous — no account, sign-in, or permission is required or offered. Nothing the Visitor does is persisted or attributed to them.

5. Core User Flows

Page 16 of 22

Flow 1 — Arriving and seeing the 3D scene (Visitor)

  1. The Visitor opens the pure-3d URL in a browser. No sign-in is requested; the page is public.
  2. The void background (#05060A) paints immediately, the split PURE 3D headline and the overlay chrome (top bar, telemetry rail, CTA, telemetry block) render, and the telemetry rail shows an initialising readout.
  3. The 3D subject — the iridescent glass torus-knot with cyan rim light and magenta core — fades in at roughly 60% of viewport height, centre-right, with the bloom pass and the 8%-opacity dust layer behind it.
  4. The idle orbit loop begins its slow 40-second rotation, and the telemetry rail replaces initialising with live camera θ/φ, zoom, frame time, and node count.
  5. Observable result: the Visitor is looking at a live 3D scene, and the headline overlaps the object's silhouette so the geometry passes behind the counters of one letter.
  6. Continuation: the Visitor can orbit (Flow 2), enter the scene (Flow 3), or scroll (Flow 4).

Failure and recovery: if WebGL is unavailable or the context is lost, the canvas is replaced by a static fallback frame of the subject with a monospace notice that the 3D scene could not start. The headline, section text, and telemetry rail remain readable and the page remains scrollable. A lost context is re-requested automatically; if it cannot be restored, the fallback frame remains.

Page 17 of 22

Flow 2 — Orbiting the subject (Visitor)

  1. Starting from the live hero scene, the Visitor moves the pointer across the viewport.
  2. The subject yaws up to ±6° and pitches up to ±4° toward the pointer with a 400ms ease-out, and the cyan orbit ring redraws its tick marks to match the new angle.
  3. The Visitor presses and drags to rotate the camera around the subject directly.
  4. Observable result: the orbit-ring readout updates (for example θ 042.7°) and the telemetry rail's θ and φ values track the change live.
  5. Continuation: the Visitor keeps orbiting, or scrolls to travel to a section (Flow 4).

Failure and recovery: if the pointer leaves the viewport, the subject eases back to its idle orientation rather than snapping. If the canvas is unavailable, no orbit is offered and the fallback frame is shown.

Flow 3 — Entering the scene from the hero (Visitor)

  1. Starting from the hero framing, the Visitor activates the bottom-left glass pill CTA labelled Enter the scene.
  2. The camera moves from the hero framing into the first content section as a keyframed move, not a fade.
  3. The section index in the top bar and the telemetry rail update to the first section, and a horizontal light sweep marks the transition.
  4. Observable result: the Visitor is inside the first section, with the inset canvas of the 3D object beside the five-column text block.
  5. Continuation: the Visitor reads the section and scrolls onward (Flow 4) or jumps to another section (Flow 5).

Failure and recovery: if the camera move cannot run, the page scrolls to the first section instead, so the Visitor still reaches the content.

Page 18 of 22

Flow 4 — Travelling through the scene by scrolling (Visitor)

  1. Starting anywhere in the scene, the Visitor scrolls.
  2. Scroll position scrubs a keyframed camera move — orbit, then dolly-in, then top-down — so the page reads as one continuous shot.
  3. Each section below the fold appears as a full-bleed dark band with a smaller inset canvas of the 3D object beside a five-column text block, laid out asymmetrically rather than centred.
  4. A horizontal light sweep crosses the object to mark the section transition.
  5. Observable result: the Visitor has moved through the scene and can read each section's content beside the geometry.
  6. Continuation: the Visitor keeps scrolling to the next section, or jumps directly to one (Flow 5).

Failure and recovery: if the camera cannot be scrubbed — reduced motion is requested, or the renderer is degraded — the sections remain reachable as ordinary scrollable content with their text intact. Under performance pressure the bloom pass and dust layer are dropped before the subject itself.

Page 19 of 22

Flow 5 — Jumping directly to a section (Visitor)

  1. Starting anywhere in the scene, the Visitor activates one of the three uppercase section links in the fixed top bar.
  2. The camera moves to that section's keyframe, and the active link takes the magenta active-state underline.
  3. Observable result: the Visitor is at the chosen section, and the telemetry rail's section index matches.
  4. Continuation: the Visitor reads the section and jumps to another, or scrolls onward.

Failure and recovery: if the camera move cannot run, the page scrolls to that section's band instead.

Flow 6 — Reading telemetry to stay oriented (Visitor)

  1. Starting from the live scene, the Visitor glances at the fixed left-edge rail.
  2. The rail shows JetBrains Mono readouts of camera θ and φ, zoom, frame time, and node count, updating live as the Visitor moves, drags, or scrolls.
  3. The Visitor uses the rail as the page's navigation index to decide where to travel next.
  4. Observable result: the Visitor knows their current position and orientation in the scene and can act on it.
  5. Continuation: the Visitor jumps to a section (Flow 5) or continues scrolling (Flow 4).

Failure and recovery: before live values exist the rail shows initialising; if the renderer is degraded or unavailable, the rail shows the last known or unavailable values rather than stale numbers presented as live.

Page 20 of 22

Flow 7 — Experiencing the site under reduced motion or a constrained device (Visitor)

  1. The Visitor opens the site with their operating system set to request reduced motion, or on a device that cannot sustain the frame budget.
  2. The idle orbit loop, light sweeps, and border pulse do not run; the scene holds a composed static frame.
  3. Drag-to-orbit and scroll-to-travel remain available, and the telemetry rail still reports camera values.
  4. Observable result: the Visitor can still view the 3D content and navigate every section.
  5. Continuation: the Visitor explores the scene at their own pace; the downgrade is non-destructive and reverses on reload.

6. Visuals, Colors and Theme

Muse: Gleb Kuznetsov. Dark voids, glowing volumetric forms, HUD-like data, and scroll-scrubbed camera moves as the hero itself. The artefact is abstract, luminous, and interactive — which is precisely "a 3D website." The register is awe and play, not commerce: the site must feel like a place, not a page.

Headline direction: Cinematic future-tech — a 3D world you can orbit with your cursor.

Page 21 of 22

Colour tokens (dark mode)

RoleHexUsage
Background (void)#05060AThe canvas itself; near-black, no white anywhere in the hero
Surface (glass)#0C1018Slightly lifted panel surface for glass overlays
Text#EAF2FFCool glassy white; 90–100% for headings, 70% for body
Primary#7CF9FFCyan light source: rims the 3D object, draws HUD strokes, colours the primary CTA
Accent#FF4FD8Magenta hot accent, used sparingly: one radial glow behind the object, one active-state underline, one hover fill
Muted#6B7A93Micro-labels and monospace data

Ratio: 80% void, 12% glass white, 5% cyan, 3% magenta.

Forbidden: blue–indigo accents (#2563EB, #6366F1, #7C3AED and neighbours); white or near-white backgrounds anywhere in the hero; the generic indigo/blue-on-white SaaS template.

Typography

  • Headings: Space Grotesk. Wide geometric grotesk. Uppercase micro-labels at 11px with 0.28em tracking. One oversized display line at 96–140px with tight −0.03em tracking and 0.92 line-height. Weight stays at 500–600; the drama comes from scale and letterspacing, never from boldness.
  • Body: Space Grotesk.
  • **Type scale
Page 22 of 22

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Rendering diagram...

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Rendering diagram...

Landing: Open site URL

Landing: Watch subject fade in

Landing: Read initialising telemetry

Landing: 1. Orbit subject with pointer

Landing: 2. Drag to rotate camera

Landing: 3. Check orbit-ring angle readout

Landing: 4. Read live telemetry rail

Landing: Enter the scene via CTA

Landing: Land in first section

Landing: 1. Scroll to scrub camera

Landing: 2. Read section content beside object

Landing: 3. Continue scrolling to next section

Landing: 4. Jump to section from top bar

Landing: 5. Read section at keyframe

Landing: View static fallback frame

Landing: Read fallback notice

Landing: Read page text while scrollable

Landing: Navigate under reduced motion

Landing: Read downgraded telemetry values