khalil.kouroghli
TUN FRContact

[05] 2026

Rayhan

A honey storefront its owner updates without a developer

01Two data filesproducts, texts, contact02Vite buildReact, static output03Static hostNetlify Drop or Vercel04Cataloguefilter by category01Two data filesproducts, texts, contact02Vite buildReact, static output03Static hostNetlify Drop or Vercel04Cataloguefilter by category
Select a box to jump to the decision behind it.

The problem

A honey brand needed a home page and a catalogue it could keep up to date itself, with no developer on call and no server to pay for.

My role

I designed and built the site, structured its content so the owner can edit it, and wrote the handover guide in plain French.

Decisions

D.01

Edit a file, not the code

Every honey lives in one products file; texts, FAQ and the WhatsApp number in a second one; colours at the top of one stylesheet. The README maps each change to the file that holds it.

D.02

A missing photo never breaks the page

Until a photo is added, the product shows a coloured placeholder. Dropping a file with the name listed for that product replaces it, with no code change.

D.03

Deploy by drag and drop

One build produces a static folder that goes online through Netlify Drop for free. A redirects file is already in place, so catalogue links work when opened directly.

What it does today

  • A home page and a catalogue with category filters, live without a server.
  • The owner changes products, prices and photos alone, following a one-page guide.
esc