What the frame is for

There is a small museum near where I grew up that has, by accident, the best entrance design I have ever seen. There is no entrance. There is a door with a brass handle and, above it, the museum’s name in a font you have to walk close to read. Inside, the first room is empty except for a bench. The second room has the first object. By the time you are looking at the object you have already, without realising, agreed to the museum’s terms: you will be quiet, you will move slowly, you will look at one thing at a time.

The frame did all of that. Not the objects.

The web makes it worse

A website’s frame is the thing every visitor sees before, around, and after the actual thing they came for. The header, the footer, the spacing, the type, the cursor — the whole machine. Most of the web’s framing machinery is leased from someone else: a SaaS template, a Notion theme, a hero-CTA reflex, the cream-coloured AI default. The visitor recognises it instantly, and recognising it instantly means they have already decided what kind of site they are on before the page has finished loading.

That decision is hard to undo. If the frame says “this is a landing page”, the visitor reads the body as marketing. If the frame says “this is a portfolio”, the visitor reads the body as a resume. If the frame says “this is a personal computer corner”, the visitor reads the body as a small museum, and is willing to wander.

Three things the frame is for

The frame, here, has three jobs.

1. Make the body legible as a kind. Before the visitor reads a word, the frame says: this is a catalog of small things made by one person, not a Substack, not a SaaS landing, not a CMS. Type pairing, color restraint, and the absence of a CTA do most of that work.
2. Set the visitor’s pace. Generous white. No urgency. No animations performing at you. The frame is what makes someone willing to click a second time.
3. Stay out of the way of the work. Once the visitor is inside a project, the frame is barely there — a small bar with the site name, a back-link, a single rose underline on hover. The project’s own world takes over.

Why I keep the chrome thin

The temptation, with a personal site, is to make the frame the work — to put the brand identity on the homepage and let the projects sit in their shadow. That is the dev-portfolio reflex, and it is exactly backwards. The brand here is the collection. Each project is a vote for what the brand actually is. The frame’s job is to step aside long enough for the next vote to register.

If the frame is doing its job, you will not remember it. You will remember the museum.