Skip to content

Food & beverage / retail

Ember & Oak

A small-batch organic roastery’s retail site: a roast shop, subscriptions, brew guides, the roastery story with its vintage Probat, and a journal.

Demo build
/04-ember-and-oak/
Orivian contribution
Full website built from zero — self-initiated, no client commission.
Site audience
Daily coffee drinkers and subscribers choosing a roaster on sourcing evidence
Pages
14 pages in the build
The Ember & Oak homepage: two hands holding a latte beside the headline "Coffee with the farmers' names on it."
Demo build · /04-ember-and-oak/ · captured September 2026

The context

What this website is for.

A Portland roastery selling transparency as hard as it sells coffee: farm names on every bag, above-Fair-Trade pay published, and a roast date the customer can check.

The reader is a daily drinker deciding whether this roaster is serious. The site converts through evidence — names, dates, sourcing — not through lifestyle photography alone.

What the site has to do

  • Get a specific coffee in front of a knowing buyer within one click.
  • Turn the sourcing story into the reason to subscribe, not a footnote.
  • Explain subscriptions without hiding the commitment.
  • Answer brew questions on the site instead of in support email.
  • Keep wholesale reachable without confusing the retail reader.

Scope

What the build covered.

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

  • Roast shop with pages for three coffees
  • Subscription flow
  • Brew guides
  • Roastery and wholesale pages
  • Journal with article pages
  • Zine-print type and ticket-card styling

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