The Wed Films
A videography studio's site has to actually play video well, which is less obvious than it sounds.
At a glance
- Client
- Aref · The Wed Films
- Year
- 2026
- Scope
- Design, build, host
- Palette
- Paper · wine · ink

Worth knowing
- 01
Built around three chapter films rather than around a gallery
- 02
FFmpeg-encoded to stream — the largest reel is 43MB, and lives off git
- 03
Enquiries relayed straight to the studio's WhatsApp via an Edge route
01The shape
The work is three chapter films, so the site is built around them rather than around a gallery. Paper, wine and ink for the palette; Spectral for the serif. Deliberately warmer and more printed-feeling than the photography archive — a different client, a different identity, not a recolour of the last project.
02Getting the video right
The chapter clips were encoded through FFmpeg to sizes that would actually stream — the largest is 43MB, and past GitHub's 100MB hard limit only because it was compressed hard first.
They're kept out of git and live on the server instead, so a deploy pulls source without dragging tens of megabytes of video through every clone.
03Enquiries that actually arrive
The contact form posts to a Next.js Edge API route that relays the enquiry straight to the studio's WhatsApp. For a studio that runs on WhatsApp anyway, an enquiry landing in an inbox nobody checks is the same as no enquiry.
Credentials for the relay are server-side environment variables on the systemd unit — never in the repo, never in a client bundle.
04Stack
- Next.js
- React
- TypeScript
- GSAP
- Tailwind
- Edge API routes
- FFmpeg
- Caddy