TX · Interactive Document Enginedrag to orbit ↻

This page is one file. No attachments, no portal, no "click to enable content." It opens in any browser, carries its own brand and typography, and — above — a live, GPU-rendered scene you can grab and spin. Scroll, and the page composes itself in front of you — every time. That is the point: a document that behaves like a product.

0×
Read-through vs. a static PDF
0+
Brand systems, one source file
0fps
Live GPU hero, in the page
0
File to send — that's the whole delivery

Why it lands

A flat PDF asks to be tolerated. A page like this asks to be explored — and the difference shows up in the only metric that matters: whether the reader keeps reading. Everything here is composed from plain text and rendered through a single branded engine, so the polish is automatic and the content stays the work.

Engagement — interactive page vs. static PDF (indexed, PDF = 100)

The same engine, real data

Numbers are first-class. The figures go in as text; the page draws them — animated, themed, value-labelled — and replays the build every time it scrolls into view.

Perceived quality climbs faster than author effort

Where the value concentrates

Where a reader's attention actually goes

Structure, drawn — not described

Process and architecture render as clean, on-brand diagrams straight from text:

flowchart LR
  A[Plain markdown] --> B{One engine}
  B --> C[Branded HTML]
  B --> D[Animated charts]
  B --> E[Diagrams]
  B --> F[3D scenes]
  C --> G((Sent as one file))
  D --> G
  E --> G
  F --> G

Reliability is the real luxury. It renders the same on every machine, every time — the spectacle never comes at the cost of the substance.

The takeaway

One source file in. One branded, interactive, self-contained page out. Send it, and the medium makes the first impression before a single word is read.