AGGREGAT
Problem
Client work under NDA proves you can hit someone else’s brief. It cannot show taste, because every decision in it was negotiated. I wanted one piece with no client and no compromise, on a subject unforgiving enough that a weak layout would be obvious — architecture, where the audience reads grids for a living.
Constraints
The practice is invented, so there was no brief to hide behind and the constraints had to be self-imposed. No photography budget, which meant working with stock and letting cropping and scale do the work. And an architecture practice is judged on its writing as much as its images, so the copy had to hold up as copy — eighteen fictional built works, each with a position, not just a name.
What I chose · Outcome
Astro rather than the Next.js and Payload stack behind CVIETA and this portfolio. That stack is the right answer when somebody has to edit the site after I leave; nobody edits AGGREGAT, so a CMS and a server runtime would have been weight with nothing to show for it. A content-driven multi-page site should ship HTML and almost no JavaScript. The layout is a Swiss editorial system — Archivo at display scale against Azeret Mono metadata rails, an oklch palette, generous full-bleed plates. A keyboard toggle draws the underlying grid over the page, so the system is inspectable rather than merely claimed. The centrepiece is one project broken into three moves — find what cannot move, take one thing away, add nothing you cannot remove — which is the case-study structure I now use everywhere, including here.
- Astro over a React SPA — content site, so near-zero client JavaScript
- Three sites, two stacks: Next.js and Payload where an owner has to edit the thing, Astro where nobody does
- Press G to overlay the grid: the layout system is verifiable, not asserted
- A real information architecture — index, work, studio, and six project routes — rather than a single scrolling page
- Swiss editorial system: Archivo display against Azeret Mono rails, oklch palette, full-bleed plates
- Copy written in the practice’s own voice, because on an architecture site the writing is half the product
- The footer states plainly that the practice is fictional — the craft is the claim here, not the client