Editorial website2026Live

PotusChef

A culinary website that translates private dinners, collaborations and ingredient-led cooking into a quiet editorial experience.

My role

UX/UI, frontend development, content architecture and CMS integration.

Current PotusChef homepage
01 / Concept

A food magazine that can become an enquiry.

The identity needed to feel refined and photographic without turning private hospitality into a cold luxury template.

The site uses strong imagery, asymmetry and slow editorial pacing to communicate craft. Underneath that atmosphere, the structure makes services, collaborations and contact pathways concrete enough for a prospective client to act.

01

Ingredients before spectacle

Photography and copy foreground material, process and shared tables rather than generic luxury cues.

02

Editorial pacing

Whitespace and alternating compositions give each story room without slowing down access to information.

03

Useful enquiries

Contact flows adapt to the request so private dinners and brand collaborations do not enter the same vague form.

02 / UX

From appetite to the right conversation.

The website balances an atmospheric browse with explicit service and enquiry paths.

01

Establish the point of view

Full-bleed photography and the ingredient-led promise create context immediately.

02

Explain the formats

Dinners, pop-ups and partnerships are separated through consistent editorial modules.

03

Collect relevant context

Enquiry forms reveal fields based on intent, reducing noise for both visitor and chef.

04 / UI system

Italian warmth, Copenhagen restraint.

Cream and bone create a tactile base, charcoal adds depth and muted sage carries active details without shouting.

Palette

Cream#FCF9F4
Bone#F0EDE9
Charcoal#1C1C19
Sage#8A9E85

Typography

TablePlayfair DisplayEditorial titles and quotes
DinnerDM SansBody, labels and forms

Components

Full-bleed heroSection markersEditorial image framesService cardsAdaptive enquiry formsCMS content modules
05 / Build

A lightweight site with an editable content layer.

The frontend is intentionally direct: semantic HTML, CSS and JavaScript with JSON-hydrated content. Decap CMS keeps content editable, while Cloudflare handles delivery and server-side form and authentication needs.

  • HTML + CSS + JavaScript
  • JSON content model
  • Decap CMS
  • Cloudflare Pages
  • Cloudflare Worker
  • Responsive accessibility

Motion principle

Slow enough to feel considered, never slow enough to block the meal.

Reveals, image scale and hover states support the editorial tone while interaction remains immediate.

Next: Meriwa