FIELD REPORT Nº 06 · CLIENT WEB DEVELOPMENT · 2026

Home Cooking with Naj

A warm culinary brand experience on the surface, with a small, secure publishing system behind it so the owner can keep the site alive.

The brief

Najwa Cagnin needed a home for a business that spans private dinners, meal preparation, cooking experiences, grazing tables, brand partnerships, and a substantial body of recipes. The site had to feel refined without losing the warmth and generosity at the centre of her work, and it had to turn interest into a clear enquiry.

I shaped the public experience around real client material: Naj's photography and story, her television credit, partner brands, guest testimonials, service areas, and recipes transcribed from her published cooking content. Iteration with Naj refined the language and presentation before launch.

The public experience

The frontend is a React 19 and TypeScript application built with Vite and a Tailwind CSS design system. A dark charcoal, cream, and gold palette gives the photography room to lead, while reusable sections keep typography, spacing, focus states, and responsive behaviour consistent across Home, Recipes, and Contact.

Visitors can explore services, filter a recipe collection, read full ingredients and methods in focused dialogs, browse curated Instagram posts, and send an enquiry with the relevant service already selected. Mobile service cards use viewport-aware interaction in place of desktop-only hover, and motion-sensitive testimonial content remains manually scrollable when animation is reduced.

DISCOVER → BUILD TRUST → EXPLORE SERVICES & RECIPES → SEND A QUALIFIED ENQUIRY

A CMS sized to the job

The owner should not need a developer to publish a recipe or replace a social tile. I built a hidden admin with Supabase email authentication and focused editors for recipes, Instagram content, and social settings. Photos are downscaled in the browser before being written to Supabase Storage, reducing upload size and keeping phone originals out of the delivery path.

Live content is stored as three versionable JSON documents in Supabase. Public reads and authenticated writes are separated by row-level security, while the publishable browser key remains safe to ship. Fresh object names prevent stale CDN images when a photo is replaced.

Designed to fail softly

A shared content provider loads recipes, social posts, and settings in parallel. If Supabase is unavailable or not configured, the site falls back to presentable seed content bundled with the application instead of showing empty sections. Loading skeletons and actionable admin errors make the network boundary visible without turning it into the visitor's problem.

The static Vite build is deployed on Vercel and instrumented with privacy-conscious route analytics. The enquiry form uses an opaque FormSubmit destination so the owner's email address is not published in the bundle, and metadata includes a LocalBusiness schema for the cities and services the business actually serves.

What shipped

The finished product is both a marketing site and a working publishing tool: brand story, services, credibility, recipes, social proof, enquiries, authenticated editing, image handling, fallback content, backup scripts, and deployment documentation in one maintainable system.

The best technical decision was keeping the architecture proportional. React provides the interactive product surface, Supabase supplies identity, data, and files, and a static deployment keeps operations simple. Each layer exists because Naj or her visitors need it.

visit homecookingwithnaj.ca ↗

A site is finished when its owner can confidently use it without you.