Scroll World 0%
Craft

The page is the argument

A summary can replace an article. It cannot replace an experience. That distinction is now the difference between a page worth building and a page worth skipping, and it is narrower than most people want it to be.

Scroll World 26 August 2026 4 min read

Two kinds of page, and only one of them is in trouble

Every page on the web is doing one of two jobs. Most are carrying information: here is the fact, here is the instruction, here is the number you came for. A much smaller number are producing an experience: they arrange time and attention so that you end up understanding something you would not have understood from a sentence.

Until recently the distinction did not matter commercially. Both kinds ranked, both kinds got clicked, both kinds got paid. Now an assistant sits between the question and the answer, and it is extremely good at the first job.

A summary of an article is a smaller article. A summary of an experience is a description of an experience, which is a different thing entirely.

The line the whole format sits on

Why scrolling is not a decoration

  1. 01Scroll is time you control
  2. 02Order carries meaning
  3. 03Scale needs distance
  4. 04Change needs sequence
  5. 05The reader does the work

Scroll is time you control

Video plays at its own pace. Text sits still. Scroll is the only common web interaction where the reader sets the speed and the page still gets to decide the order.

Order carries meaning

If the reader cannot see the conclusion before the setup, the setup can actually do its job. That is not possible in a page they can skim.

Scale needs distance

You cannot show how large something is on one screen. You can show it across four screens of scrolling, and the scrolling is the measurement.

Change needs sequence

A before and an after next to each other is a comparison. A before that becomes an after as you move is a demonstration.

The reader does the work

Which is the entire point. Something you had to move through is remembered differently from something you were told.

The honest limit

Here is the part that most arguments for this format leave out.

An assistant does not have to be a substitute for your page in order to cost you the visit. It only has to arrive first and be sufficient. Somebody who wanted a number, got the number, and closed the tab was never going to grade your page against it. They finished their task.

So the format protects you only on questions where a sentence does not finish the job. That is a real category and it is a much smaller one than "things worth writing about".

The test, applied

Do not build this

How tall is a blue whale. What year did the company launch. Which of these two plans is cheaper. What does this acronym stand for.

Every one of these has a correct one line answer. A beautiful page about any of them is a slower route to a sentence, and it will lose, deservedly.

Build this

How the whale compares to everything else in the ocean, at scale, in one continuous movement. How a plan's cost changes across every usage level you might land on. How a process actually unfolds when you are inside it.

None of these compress. The compression is what you were trying to avoid.

Four questions before building anything

  1. Can a sentence finish this?

    If yes, write the sentence. Publish it as a paragraph, or do not publish it at all. Do not build a page to lose to a summary.

  2. Does the order matter?

    If a reader could take the sections in any sequence and lose nothing, this is a list, and a list should look like a list.

  3. Is there something here that only movement can show?

    Scale, change over time, accumulation, a process. If none of those apply, the scrolling is decoration and decoration is a cost.

  4. Would you scroll it twice?

    The second scroll is the honest test. The first can be carried by novelty.

What this means for the craft

Once you accept that the experience is the product, a lot of the usual advice inverts.

Loading fast stops being a technical nicety and becomes the whole first impression, because an experience that stutters is not an experience. Working without JavaScript stops being a checkbox and becomes proof that the argument survives outside the animation. Respecting somebody's request for reduced motion stops being an accessibility line item and becomes a test of whether the page still says anything when you take the motion away.

If the page collapses under any of those, the motion was carrying it. And motion that is carrying a page is decoration wearing a serious face.

0
Pages here that fail the sentence testby rule, not by luck
400 KB
Hard ceiling on page weightenforced at compile time, not checked afterwards
100%
Of content readable with JavaScript offincluding this one

Why we are writing this down

Publishing the rule is how it survives contact with a deadline. A standard you have written in public is harder to quietly drop on a Friday than one you only told yourself.

Every page on this site is compiled from a plain text file by a library of scroll mechanics, and then deployed without anyone touching the markup. That is the machine. The rule above is what decides whether we point it at something.