Skip to content

Fashion / editorial

SNITT

A fashion house site that behaves like a look book: a slideshow of collection looks, four collections, an archive, a journal, stockists, and contact.

Demo build
/01-snitt/
Orivian contribution
Full website built from zero — self-initiated, no client commission.
Site audience
Press, buyers, and clients following a fashion studio’s collections
Pages
15 pages in the build
The SNITT homepage: a black-and-white editorial photograph of a model in striped trousers beneath the SNITT wordmark, with look numbering and a View Look control.
Demo build · /01-snitt/ · captured September 2026

The context

What this website is for.

A fashion design studio presenting collections to press, buyers, and clients who read restraint as confidence — the site is the look book, and it has to feel like an archive rather than a shop.

Nobody arrives here to buy a product SKU. They arrive to judge taste, and typography, sequencing, and whitespace make that judgment before any garment description is read.

What the site has to do

  • Present each collection as an editorial body of work, not a catalog.
  • Number and caption looks so a reader can reference them.
  • Keep archive and journal one step behind the current collection, never in front of it.
  • Give stockists and studio contact a quiet, credible path at the end.
  • Read as luxury with no decorative help — no badges, no sale flags, no noise.

Scope

What the build covered.

Structure, content, design, and build for the whole site — the parts a visitor can see and use.

  • Hero slideshow with look numbering
  • Collection index and four collection pages
  • Archive and journal with article pages
  • Stockist listings
  • Editorial typography and spacing system
  • Responsive layout across devices

Related services

How this translates to your project.

These are self-initiated demo builds. No client commissioned them; brands are fictional or fictionalized, and prices, hours, and metrics inside the demos are labeled indicative.

Planning a clearer, more useful website?

Describe what you are building and what needs to be clearer. The conversation starts with the problem, not with a package.

Remote · Direct · No pressure to choose the biggest package