Layouts

MATERIALS.
FIVE WAYS TO SPLIT THE SAME INFORMATION
PICK BY NUMBER
SUBJECT. disk, structure, models, recommendations
ALTERNATIVES. 5 · the current build is 02 plus a fourth page
RULE. answer with a number, or two, and I rebuild
NOTE. all five are built from the same snapshot, so switching is cheap
01

Ways to split it


LAYOUT 01sheet

One continuous sheet

Everything on a single scrolling page: disk, structure, models, recommendations. The axonometric figure sits at the top as the single entry point and the reader scrolls.

  • One URL, nothing to navigate
  • Works on a phone with no thought
  • Gets long, and disk and models are different kinds of information

Best when you mostly come to check one thing and the page is a habit, not a destination.

LAYOUT 02index

Three pages, one index

A thin index that holds only the figure and the headline numbers, then a separate sheet per subject: disk, models, layout. The index is the poster, the sheets are the reference.

  • Each subject gets its own density
  • The index stays worth looking at
  • Four URLs instead of one

Best when the subjects genuinely have different reading rhythms, which they do: disk changes daily, models change weekly.

LAYOUT 03tabs

Tabs over a single document

One page, three tabs, no navigation away. Tab state in the URL hash so a view is still linkable.

  • Feels like an instrument panel
  • Switching costs nothing
  • Deep links need care, and print is awkward

Best when you are comparing models against disk and want them side by side in your head.

LAYOUT 04cards

One card per subject

A grid of cards, one per owner of space and one per paid plan. Click to expand in place. The ledger and the model catalogue are the same object seen two ways.

  • Disk and models share a visual grammar
  • Scannable, almost no prose
  • Deep detail has nowhere to live

Best when you want the overview on a wall and never read the paragraphs.

LAYOUT 05dossier

Static dossier, refreshed on a timer

One build, no interaction at all. Numbers are baked at build time, the site is a document that gets replaced. A diff between two dates is the only navigation you need.

  • Cannot go stale, it is a snapshot
  • Renders anywhere, even a text browser
  • No way to drill into anything

Best when the value is the record, not the browsing. This is also the honest option for a machine you do not sit in front of.