Argue about structure before it costs anything
Technology
Relume is a library of conventional page sections plus a generator that turns a description of a company into a sitemap and wireframes. It is not a design tool and it is not a build tool. It is a way to settle what the pages are and what order the sections go in.
We used it on Orb's site to carry early layout exploration and content structure, validating page flows and hierarchy before final design. Narrowing the options early meant fewer revisions later. What shipped is Next.js, Tailwind, and Sanity.
Process
Where Relume helps, and where it stops helping
- Structure gets settled before anyone picks type
On Orb it carried early layout exploration and content structure, so page flows and hierarchy were validated before final design. Moving a section in a wireframe costs nothing. Moving it in a finished comp costs a day, and moving it after the build costs a sprint.
- Generic components are the point and the limit
Hero, feature grid, logo wall, FAQ. The library is a vocabulary of conventions, which is exactly what makes the pieces fast to rearrange and useless as an identity. Everything that makes a site look like one specific company happens after Relume is closed.
- It has nothing to say about product UI
Relume assumes marketing page types. A dashboard, a configurator, or any application surface has no conventional section order to borrow, because there the layout question is the product question. Nothing Relume produced appears in Orb's running site, which is the right outcome.
