Design work deserves the public record code already has

GitHub turned code into public careers. A handle, a profile page, organizations with identities of their own, repositories living under one of them, each repository choosing its own visibility. Commits became reputations. Somewhere along the way the profile became the résumé, and Google started finding developers through the work itself.

Design never got that. Great design work lives inside private files and mostly dies there, the portfolio is a separate chore designers maintain by hand, and most tools treat public as an afterthought attached to a collaboration model. The work happens in one place. The career gets assembled somewhere else, by hand, on nights the designer would rather be designing.

Wonder chose the GitHub direction.

Identity is public first

Every person who signs in gets a handle and a Personal workspace. No setup ceremony. Organizations carry the same shape under their own name, handle, profile, and members, so a studio or a product team is a public entity the way a person is.

Profiles are public pages. They show identity fields and the public files and folders of that home, while private work and member rosters stay out of the anonymous view. What a visitor sees is the part of the record its owner chose to show.

Every file lives under a name

There is no anonymous pool of documents. Every file lives under exactly one person or organization, the handle is part of the file URL, and you can see who a file lives under before the canvas loads. Open a handle and you land on a person or an organization. Open a file below it and the name stands above the work.

This is the relationship repositories have to people and organizations on GitHub. The name comes first. The work accumulates under it, and over time the body of work under a name starts to mean something on its own.

Files choose their own visibility

Files start private. You flip a file public one file at a time, the way visibility belongs to each repository on GitHub.

A public Wonder file opens the live canvas for anyone. No sign-in, no exported copy, no publication snapshot drifting out of date while the team keeps working. An anonymous visitor reads the same live document the team is editing, collaborator cursors and selections are not shown to public viewers, and going private again closes public access and removes outside readers.

The work stays yours throughout. Wonder's Terms are explicit that users keep ownership and the intellectual property rights in what they make.

Findability is what we are building

Here is the mission stated plainly. We want a designer's profile to be a page Google can find, work that compounds into a visible track record, organizations that show their design culture in public, and a portfolio that exists as a byproduct of simply doing the work.

That is direction, not current behavior. Public today means a file opens without sign-in and appears on its home's profile. Search indexing and discovery are the parts we are still building, and we would rather say that plainly than imply a feature that does not exist yet. The architecture underneath is already in place, since a public profile with public work under one handle is exactly the kind of page findability gets built on.

The organizing principle is the difference

Figma is a superb collaboration tool organized around the team and the file, and its Community is a separate publication flow with its own snapshots and update cycle. Paper and the newer canvases are earlier on this path and still building out their sharing models. Lunacy already pairs cloud documents with a public web profile.

Every piece here has precedent somewhere. What separates these products is the principle each one organizes around. In Wonder, public identity sits at the center, and homes, files, visibility, and profiles all hang off it.

Two limits we will not hide

Membership is home-wide today. Inviting someone joins them to the whole Personal workspace or organization around the file, so we still cannot invite one person to just one file. Files also cannot move between homes yet, which means work that starts under the wrong name stays there for now.

A model that puts a public name above every file has to be honest about its seams, because the name in the URL is a promise about who stands behind the work. Both limits are on our list.

The portfolio becomes a byproduct

A developer's reputation today is largely the residue of shipped work under a public name. We think design careers can work the same way, where the profile is simply the place the public work already lives and the track record is whatever accumulates while you keep designing. The best portfolio is the one nobody had to build.