platform Case study
Yasi Gallery USA
On a gallery site the photography does most of the selling. I built this one to show the work at the size and quality it deserves, and then to get out of the way.
The business problem
Gallery and premium ecommerce sites fail in two directions. Either the design competes with the work being sold, or the site is so custom that adding a new piece takes a developer. Both are common, and both are avoidable.
What I delivered
- A gallery-first presentation that gives images the space and the loading priority they need.
- An ecommerce structure built for a considered, low-volume purchase rather than a high-turnover catalogue.
- Visual positioning that matches what the US market the business sells into expects.
- A WordPress build the owner can maintain, so adding or changing work is an ordinary content task.
Technical approach
- I agreed the scope against what the business actually needed, instead of proposing a platform build for a site that did not require one.
- I stayed close to standard, well-understood patterns, because the client's own team maintains the site after handover.
- I treated content structure as the main design problem, since navigation decides whether a visitor finds what brought them.
- I added nothing the owner would need a developer to change later.
Result and evidence
The gallery shows its work at the quality the market expects, and the owner adds new pieces without calling a developer.
Commercial value
A gallery's inventory changes constantly. If every update carries a cost, the site stops being worth having.
Readable implementation brief
implementation_brief {
project: "Yasi Gallery USA"
type: "gallery + ecommerce, US market"
priority: "the work itself; the design does not compete"
purchase_model: "considered, low volume -- not high turnover"
platform: "WordPress, deliberately plain"
constraint: "owner adds work as ordinary content editing"
}What this project shows
Restraint is the design skill this kind of project actually needs. The site should not be the most interesting thing on the page.
A client's site stays current only when routine content changes are genuinely routine. That is what I optimise for here.