Kozi's
A ground-up website rebuild for Kozi's — a seven-page production site (menu, story, visit/contact, gallery) built in vanilla HTML, CSS, and JavaScript — paired with an ongoing monthly retainer covering photography, social content, and seasonal campaigns.

The Problem
Restaurant identity work usually happens in one of two modes: an expensive rebrand delivered once, or an unmanaged social account posting whatever's on hand that week. Kozi's needed a third mode — a system light enough to run monthly, disciplined enough to still look like one restaurant a year later.
My Role
- WEB
- PHOTO
- CONTENT
- FRONT-END
Process
- 01
Context
An ongoing retainer relationship with a restaurant that changes its offering seasonally and relies heavily on repeat, local custom rather than one-time tourist traffic — which changes what an identity needs to do. It isn't attracting strangers; it's rewarding people who already know the place.
- 02
Research
Rather than a formal brand audit, the early work was observational: sitting in the restaurant across several services, noting what regulars actually said about the food and the room, and which of the restaurant's own instincts about itself were accurate versus aspirational.
- 03
The Constraint
No dedicated content budget for elaborate shoots each month. Every campaign had to be plannable and shootable within the restaurant's normal operating rhythm, using the light and setting that already existed rather than staged additions.
- 04
Creative Thinking
The identity is built on consistency of behavior rather than a fixed template — the same approach to framing, caption tone, and posting rhythm applied every month, so the presence reads as continuous documentation of the restaurant rather than a rotating set of campaign graphics.
- 05
Iterations
Early social content leaned heavily on plated-dish photography, which is the default for restaurant accounts and, predictably, looked like every other restaurant account. The identity found its footing once the camera moved toward the room itself — hands, counters, the specific light Kozi's gets in the late afternoon — rather than the plate alone.
- 06
Process
The site was built page by page in vanilla HTML/CSS/JS rather than a framework or template, with a custom photo-processing workflow developed specifically for consistent color and exposure across restaurant photography shot in mixed, often difficult lighting. Alongside the site build, an ongoing monthly cycle covers a shoot, edit, and post cadence for social content and seasonal campaigns.





What Changed
A deployed seven-page production site, plus a running monthly content and photography retainer that continues alongside it.
The temptation with any ongoing retainer is to keep adding — more content types, more channels, more polish. The more useful discipline has been knowing what not to add. Kozi's identity has stayed legible precisely because it hasn't tried to become a bigger idea than the restaurant itself.