gno.sh Publishing

Publish a note

The fastest path from a note on your disk to a published reading surface on gno.sh.

Open the signup page and create a free account — no credit card required. You’ll get a verification email and land on your dashboard.

2. Open the publish studio

Go to the publish studio. The studio is the producer surface — it shows your source list, visibility modes, metadata projection, and an import drop zone.

3. Drop or import a file

Canonical path: export from local GNO first, then upload the artifact.

gno publish export atlas --out ~/Downloads/atlas.json

Then open /studio and drop that compiled GNO artifact JSON into the import zone. The markdown path is still useful for quick single-note shares in dev, but the artifact JSON is the real hosted transport for larger collections.

For public, secret-link, and invite-only uploads, the studio can now create a new space, overwrite an existing space, or append the new notes into an existing space so the left-hand navigator grows over time. Encrypted shares still update via fresh encrypted upload only.

4. Pick a visibility mode

Public — a plain URL anyone can read
Secret link — an unguessable token. Rotate, revoke, or expire at will.
Invite only — members of your org sign in to read
Encrypted — client-side passphrase. We store ciphertext only when the artifact was encrypted locally before upload.

5. Press publish

A receipt appears with the share URL. Click Open to see how your reader will experience the page — full editorial typography, outline, scoped search, and keyboard navigation.

Republish

Re-importing the same route slug replaces the existing share with a new snapshot. If you want to grow a published collection instead of replacing it, choose Append to existing in the studio. Readers keep the same URL in either case; append adds notes to the navigator, overwrite replaces the snapshot.