← Back to selected work

Still under construction — this write-up is still being added to

StoryFlow Africa

Site for a film and photography studio shooting the whole range of African life — hospitality, wildlife, culture, brand work and stage — at a craft level that never sands the people out of the frame.

Role
Design and development
Stack
Design & buildNext.jsMotionPerformance

The brief, and the one test

StoryFlow Africa is a film and photography studio — one photographer and filmmaker working as a studio, shooting hospitality, wildlife, culture, portraiture, brand film, stage and sport. Radisson Blu, The Mora, ALU, View the Wild and TAZAMA are on the client list.

For a studio, the site is the pitch. When a hotel or a university is deciding whether to hand this studio a budget, part of what they are judging is how the work is put in front of them. So every decision on the build got measured against one question: does this make the photography land harder, or does it get in the way?

Under that sits the thing the whole site has to prove — that technical excellence and honest, human storytelling can be true at the same time. Polish that sands the people out of the frame fails the second half. Anything that reads like a generic agency template fails both.

The opening frame — the showreel, and one line
StoryFlow Africa homepage: 'Africa, in full.' over a still of two people walking through tall grass

One scroll, not a menu of pages

The obvious build is a homepage that links out to Work, Services, About and Contact. We didn't do that, because the studio's argument only works in order.

It opens with the film. It states what the studio has done. It makes its case about how Africa usually gets photographed, then shows the breadth, then the proof, then puts a real person behind it. Each section sets up the next. Someone landing on a standalone Services page gets none of that build-up.

So the site is one continuous scroll, and the navigation jumps within it rather than away from it. Four destinations — Our Services, Our Works, Studio, Contact — all live on the same page. The single exception is a project, which genuinely earns its own room and is reached by clicking the work, not the menu. Two page types in the entire site; nothing else earned one.

The trade-off: there is no full index of all work. The featured stack is the index. If the catalogue eventually grows past what anyone will scroll, that is the decision to revisit first.

Making the photographs load fast

This is a photography site loading over East African connections. If the photographs are slow, the site has failed at the only thing it is for. This took more work than anything else.

The core problem: the hero showreel is 87 seconds of video — 18.5 MB at source — downloading over the same connection as the 82 KB still that is actually the first thing you see. The still lost that race every time. That is why images "took a moment to show": they were queued behind a film nobody had asked to watch yet.

The fix follows what the visitor is actually looking at. They are looking at one still, so everything else — including the film that will eventually replace it — can wait its turn. The film is now held back until the still is on screen, and buffers underneath the loader, which is time the site was spending anyway. By the time the loader clears, the film is already running.

The second problem: an image that hasn't arrived is a grey box, and a page of grey boxes reads as broken. Now every frame ships with a tiny, heavily blurred version of itself — around 200 bytes, small enough to arrive with the page — so you see the real composition and its colour immediately, and it sharpens from there. Nothing on the page is ever empty.

The rest is just discipline. The browser is told where images are coming from before it has finished reading the page. Phones are never sent desktop-sized files. Nothing is served larger than it is displayed — the backdrops behind the stat numbers were arriving at full resolution and then getting blurred almost to nothing, five times the file for a picture you cannot even make out.

Motion that behaves like a camera

The temptation on a site like this is to animate everything, which is exactly what reads as a template. The rule we used instead: if a movement isn't something a camera or a photographer actually does, it doesn't belong.

So things resolve out of soft focus, the way a lens finds it. The thesis section makes its point with a crop — cropping is what a camera imposes on a place, and that section is about how Africa gets framed. The loader is an ISO dial.

Two rules sit under all of it. First, arrivals happen once: a section announces itself and then holds still, because anything that loops competes with the photographs, and the photographs should win. Second, where something does move continuously, it is tied to the visitor's own scroll, at their pace — the page never takes the scroll away from them.

Every one of these has a real reduced-motion fallback — the same content, plainly presented, never a broken version of it.

A loader that's doing real work

There is a loading sequence: an ISO dial climbing through real camera sensitivities on black. It isn't decoration. It is waiting for the first images to actually arrive and be ready to draw, and the gauge reflects that real progress rather than a fake timer.

It used to run on first visit only. That was wrong — it meant the site opened one way for a new visitor and simply skipped the opening for anyone returning. It runs every time now, but a returning visitor gets the same dial swept in under a second instead of sitting through it again.

The gauge is real progress — bytes arrived and images ready to draw
The loading screen: an ISO dial on black reading 4000, its arc lit orange

Not writing the client's words for them

The studio has the photographs but hasn't written the copy yet. This was the most important call on the project.

The easy path is to fill the gaps with plausible-sounding text — a project description here, a results figure there. We didn't, anywhere. Nothing on this site claims anything the studio hasn't actually said: no invented project stories, no made-up numbers, no stock photo standing in for work that doesn't exist, no photograph filed under a category on a guess.

Where copy is missing, the space is held open and clearly marked rather than filled. You'll see it on the founder's portrait, on the story section of each project page, and on any category with no work supplied yet.

The reasoning is simple: a sentence under a client's name is a claim about that client. An institution weighing up this studio isn't helped by a brief the studio invented on their behalf — and would notice. A frame that is clearly waiting reads as a studio with standards; a fabricated one reads as a studio that will make things up. And it costs nothing to keep open — each gap is one line of content dropped in when it is ready.

The template bends to the photograph

Project pages share one template, but it lays itself out from each image's real shape. One client's film was shot vertically, for a phone — so it gets a vertical stage instead of being letterboxed into a horizontal one. Two of the stills are portrait, so they are shown as portraits, not cropped square to match their neighbours. On its own page, a photograph runs uncropped at the size it was made for.

Cropping a photographer's composition to tidy up a grid is the one thing a portfolio template shouldn't do.

Adding work is a content job

The studio keeps shooting, so adding work had to be easy. A new project is one entry in one file — name, images, film if there is one — and the page builds itself. New photographs in a category work the same way. No layout work, no new components, no developer needed for the routine case.

Three languages from day one

English, French and Swahili shipped together, rather than English-first with translation bolted on later — because retrofitting that is a rebuild. No text is baked into the design; it all lives in one file per language, so a fourth language is a file, not a project.

The close — prints on a table, and one ask
StoryFlow Africa contact section: 'Let's make them feel it.' ringed by scattered photo prints

What it came down to

Nearly every decision traced back to the same question: does this serve the photographs, or does it serve the interface? Anchors instead of routes. A film that waits its turn. A loader measuring real progress. Placeholders that admit what is missing. Each one is that question, answered in favour of the work.

Built with Next.js on the App Router, fully static per language, Tailwind, GSAP for motion, Cloudinary for media, next-intl for languages, deployed on Vercel. Everything ships as files, and the heaviest thing on the page is the thing people came to see.