🖼️
Show the work.
Portfolio hosting
The one project with no client. It represents whoever built it, which makes it the hardest brief there is.
Built with
Built by
Features
Benefits
Solutions
The one project with no client. Nobody wrote the brief and nobody signs it off, but it decides whether the next piece of work turns up. The discipline barely matters — photographer, illustrator, audio engineer, developer — the shape is the same: a body of work a stranger can take in quickly, plus a way to make contact.
Very little logic, a great deal of media
PHP renders a handful of templates and stops; the weight is in the media. Every environment books storage as a required component — a persistent file system with SSH and SFTP access, so uploads survive deploys instead of living inside a build. Media committed to the repository ships with each git push, which suits a site that changes twice a year.
Quiet for months, then vertical for two days
A portfolio gets a trickle until a project is picked up somewhere. Almost all of that traffic is anonymous reads, so the CMS's page cache absorbs most of it before PHP does real work — and the PHP component can be scaled up for a few days and back down, each day billed at 1/30th of the monthly rate.
There's no retainer attached, so the site gets attention in bursts. A flat-file CMS keeps content in the repository: no database component to book, nothing to patch between updates, and the whole site restores from a Git clone plus one rsync of the uploads.
Trust
An honest account.
