Publishing on the web

The Publish menu puts a document, or a whole workspace, on usevizzy.com, so you can send a teammate a link instead of a screenshot. You can also publish from the terminal. See Publishing from the CLI.

Publishing a workspace is private by default. It uploads the content and gives you a link, but until you share it, that link only works for you. Choosing who can read it is a separate step. See Who can read it below.

Sign in

Publishing is tied to your account, so the first time you publish you sign in with GitHub. The app and the CLI share one account. Sign in on either and the other is signed in too.

Publish a document or a workspace

The Publish menu has two options:

• Publish this workspace publishes every document across the workspace’s watched folders and attached files as one browsable site, with a collapsible file-tree sidebar and a document switcher. New workspaces start private. Sharing… opens the controls. Copy link to workspace copies the link again.
• Copy link to this document publishes the document you are looking at as a public page and copies its link to the clipboard. This link is always public. Use “Publish this workspace” if you want to choose who can read it first.

Republishing updates the same link. Publish again after an edit and the URL does not change. Republishing never changes sharing you have already set up: a public workspace stays public, a code-protected one keeps its code, and the code itself does not change. Cross-file links between published documents resolve and open in a new tab. Your vizzy.config theme travels with the workspace, so published pages look like they do in the app.

Who can read it

Click Sharing in the top right of a published page you own, or on the workspace’s row in your library. Publish ▸ Sharing… in the app opens the same dialog. There are three settings:

Setting	Who can open the link
Private	Only you, signed in. The default for a new workspace.
Password-protected	Anyone who has the link and types the code.
Public	Anyone with the link.

Published pages are never listed anywhere and always carry noindex, so search engines will not surface a public workspace. “Public” means anyone with the link, not findable.

Share codes

Choosing Password-protected generates a readable code like plum-otter-7k4mx. Send the link and the code, ideally in different places. The reader types the code once. The unlock lasts 30 days in that browser.

You can copy the code, or type a different one and save. Saving a new code, or switching away from Password-protected, immediately locks out everyone who unlocked with the old one.

A share code is a shared secret, not an account

Anyone you give the code to can pass it on, and you cannot tell who used it. Treat it like a door code for a meeting room, not like a bank password. It is good for keeping a work-in-progress off the open web, not for anything confidential. Per-person access control is a separate feature, still to come.

If you type your own code, do not reuse a password from anywhere else. Codes are stored so that you can read them back later.

Reading vs. canvas mode

A published page can be read two ways, chosen from the view-mode dropdown in the reader header:

• Document (the default): the file renders as a scrollable reading document. It shows a readable column of full Markdown (headings, lists, quotes, tables, code) with the diagrams embedded inline and a floating heading outline.
• Canvas: the same pannable canvas you see in the app.

The choice is reflected in a shareable URL, ?mode=document or ?mode=canvas, so you can send a link that opens in the view you want.

Expand a diagram

Every published diagram has an expand button. It opens that diagram alone in a full-screen pan-and-zoom modal, centered and fitted, so you can look closely at a dense diagram without the rest of the page.

Manage what you have published

Your library lists everything you have published, with each workspace’s current sharing setting on its row. Deleting a workspace there removes its published content from the web.