May 2026 · Profound
The Pages surface
The screen editors use to reason about site structure, and what it has to admit it doesn't know.
Pages is where an editor sees how the site is put together — what routes exist, what content is bound to them, what will actually resolve. I built and iterated most of this surface; a colleague holds the rest.
The design problem
The honest state of a page is more complicated than 'published'. A page can exist, have content, and still not be reachable because its route has no binding. Showing that as a normal page is a lie. Hiding it is worse.
So the surface distinguishes bindings that were set manually from ones resolved automatically, and it renders a distinct preview state for pages that currently cannot route. It is less tidy than a uniform list. It is also the only version that tells the truth.
The route rename flow from the migration engine lands here too — this is where an editor triggers a rename and reviews what the resolver wasn't sure about.