Frontend ✦ 08 Aug 2026 ✦ 8 min read
Making route changes feel like the story
A page transition is a sentence about what just happened. Say the right one.
Every site has a moment where the old page stops being the page. Most of them spend that moment in a flash: a white gap, a repaint, a new document. The user did not ask for that moment, and they cannot do anything with it.
A site built as a story has a different problem. Its sections are pinned, they swing in, and the page is meant to be read in order. If a route change hard-cuts, it does not just lose polish — it breaks the metaphor.
The transition is not decoration on top of the navigation. It is the navigation, given a shape.
The moment between
You have been reading a book, and now you are looking at a different website. The transition has to belong to the same world as the story.
Ours slides: the old page leaves at the top, the new one arrives from below, both at the same speed, so they tile without a gap. It is the same gesture the panels make when one hands over to the next.
The mechanics
The mechanics were the easy part. The browser has a view transition API, the framework can pair the outgoing and incoming pages, and the whole thing is a few lines of CSS on the root snapshot.
The hard part was what to leave still: the navigation does not move, because a moving header takes the reader's anchor with it.
One place
None of this is subtle once it works, which is the point. A transition should not be the thing you notice.
It should be the thing that makes you believe the site is one place.
Next note