Brand · proof
Every product site wants a wall of customer quotes. This site cannot honestly have one yet — there are no customers to quote — so it does the next honest thing: it writes the three stories it wants to be able to tell, with the names and numbers labelled as invented examples until a real builder says something themselves.
The handles below (linnea.dev, mikef.builds, studio.noir) are demo personas authored for this library. The builds are described in the sample data that also powers /samples, and their sizes are estimated page weights from those files — not third-party measurements. Nothing here is a real person's endorsement, and the page says so before any quote appears.
A pre-launch SaaS had a two-line landing page and a conversion problem: nobody could picture the product, so nobody joined the waitlist.
A single-screen build — a wipe-revealed headline, a tilt signup card, a logo strip for the 'trusted by' row and a loader that doubles as the saving state — lifted waitlist signups from 2.1% to 6.4% in the first month.
A developer's portfolio read like a résumé — bullet points and dates — and recruiters were not staying past the first screen.
The rebuild turned the work into a night-sky scene: an orbit ring of case cards, scramble-text reveals, and flip cards that hide the details until you want them. Time-on-page tripled.
A developer tool's landing page explained the product with adjectives; users could not tell what the tool measured or why it mattered.
A data-first build — morphing backdrop, a tab-morph product tour and a live-feeling momentum chart — replaced the adjectives with evidence. Trial starts rose 31%.
A quote earns its place here when three things exist: a named builder who said it, a build that can be opened, and a number that came from outside this repository. Until all three are true, a story stays in this section with its label attached. The alternative — an unattributed “loved by developers” badge — is the kind of line this whole site is built to avoid.
The sample builds themselves are real code paths: each one is assembled from components that exist in the catalog, and each is one click from the /samples pages where the stack is listed.