Designing an OS, Not a Website

The constraint that shaped everything

Most portfolios are corridors. You walk through them in the order the designer intended, nodding politely at each project. We wanted something closer to a desk, a place where the work sits in windows, panels, and lists you can rearrange in your head. Framing the site as an operating system gave every decision a rule to answer to: does this feel like part of the machine, or like decoration taped on top?

The metaphor earns its keep in the details. Navigation becomes a sidebar of system folders. Project meta lives in panels with title bars. Even the small yellow status dot in the sidebar is doing real work. It tells you whether the studio is taking on new projects without a single line of marketing copy.

Folders, not funnels

The first thing the metaphor killed was the marketing funnel. An operating system does not usher you toward a call to action; it presents a set of places and trusts you to choose. So the sidebar became a file tree, the topbar a system strip with a command palette, and every page a window into the same machine. Visitors stopped being led and started browsing. Session times went up, and the contact rate, oddly, rose with them.

Navigation had to earn the metaphor too. We named routes the way a file system would: work, about, contact, playground. No cleverness, no invented verbs. The pathbar in the corner prints the current location like a terminal prompt, which sounds like a gimmick until you watch someone use it to orient themselves. Wayfinding is just typography wearing a uniform.

The deeper win was editorial. When every section is a panel, you cannot pad a page with vague slogans, because a panel with nothing in it looks broken. The system forced every block to carry real data: capacity, availability, shipping status, actual project years. Honesty became a layout requirement.

The details that sold it

Window chrome did more work than any headline. Three dots and a mono label turn a plain card into a place, and once cards are places, the site feels inhabited. We reused the pattern sparingly (project specs, the studio card, this blog) so it stays a signature instead of wallpaper.

The boot loader was the riskiest indulgence: a percent counter, a wordmark reveal, half a second of theatre. It survived because it sets the contract early. This site behaves like software, not like a brochure. People forgive a system for loading. They do not forgive a poster for it.

And that status dot is the whole philosophy in eight pixels. It is live, it is honest, and before a single sentence gets read it answers the only question a prospect actually has: are they taking work?

What we would tell a younger studio

Pick one organising idea and let it boss you around. A strong constraint is not a cage; it is a colleague with taste. Every time we were tempted to add a section, the OS metaphor asked whether the system actually needed it. Usually the answer was no, and the site is better for every one of those refusals.