Sharing & sessions

There are no accounts and no saved projects — a session is a link. Share link (in the main menu) encodes your entire state — scale, every palette, typography, grid, effects — compresses it, and puts it in the URL after #s=. Anyone opening the link lands in exactly your session and can keep working from there.

Three properties follow from this design:

• Nothing is uploaded. The state travels in the URL itself; the server computes ramps and exports from what the link contains but stores nothing. Close the tab and the session exists only where the link exists.
• Links are durable. A link is a complete description, not a pointer into a database — it cannot dangle, expire, or 404.
• Links compose. Every guide in the learn section ends in a link that opens the tool with a curated example preloaded — the same mechanism you use to share work with a colleague.

Undo and redo

History spans the whole session — color edits, type steps, grid changes, all in one stack (⌘Z / ⇧⌘Z, or via the main menu). Rapid sequences like holding an arrow key coalesce into a single undo step, so undo moves in meaningful strides rather than pixel increments.

Language

The interface ships in English, Swedish, Spanish, and Chinese. A ?lang= parameter on any link opens the tool in that language — useful when sharing across teams. Content you have written (specimen text, breakpoint labels) is never translated behind your back.

What the browser stores

Only two small preferences live in localStorage: your language choice and whether you have seen the intro. Your design work is never persisted locally or remotely — the link is the artifact. If you want a checkpoint, copy the share link; if you want history beyond the undo stack, keep links the way you keep git tags.