grove

Publishing

Publish any Grove note — or a whole folder — as a hosted, read-only web page you can share by link, gate to your team, or make public. The published page is rendered by the same engine that draws your notes, so what you share is exactly what you authored: prose, code with syntax highlighting, tables, Mermaid diagrams, kanban boards, and [[wikilinks]].

It's free. There's no per-seat cost — publishing rides on the same GitHub sign-in you use to own your links.

Signing in

Publishing is the one place Grove asks you to sign in. Connect GitHub from Settings → Account (or when you first hit publish). That sign-in is how published docs are owned — only you can change or unpublish what you've shared — and how organization gating works. You sign in once; Grove stays signed in across restarts.

Publishing a note

Open a Markdown note and click the Share icon in the editor header. That's the whole step — one click publishes the note as an unlisted link and copies it to your clipboard. No modal, nothing to configure first.

Once it's live, the Share control becomes a pill that opens the published page, with a caret to copy the link again. From then on the page updates automatically every time you save — no re-publish step. People with the link always see your latest version.

Visibility

Every published doc starts as an unlisted link. To change who can see it, open the published page and use its Share menu:

  • Anyone with the link (the default) — the link is the key. It's never listed anywhere and search engines won't index it. Best for quick shares — but don't use it for true secrets, since anyone the link is forwarded to can read it.
  • GitHub org — visitors must sign in with GitHub and be a member of the org you choose. Right for private team docs. (Membership is read from the viewer's own GitHub account — you don't need to be an org admin.)
  • Google Workspace domain — the Google analog: visitors sign in with Google and must be on your Workspace domain.

Readers of gated docs see a polite sign-in page; anyone else gets "you don't have access." You can also rotate a link at any time — the old link dies and a fresh one is minted — or unpublish entirely.

Publishing a folder as a site

A single link is great for one doc. A collection turns an entire folder into a navigable site — sidebar nav on the left, your docs on the right, with the folder structure preserved.

Hover a folder in the sidebar (or right-click it) and choose Publish folder. Grove publishes every Markdown file in the folder and its subfolders as one collection with one link and one visibility setting.

  • Nested folders are kept — subfolders become collapsible groups in the nav.
  • Links between your notes just work. A [[wikilink]] to another note in the same folder becomes an in-site link; links to notes outside the published folder stay plain text, so you never accidentally leak an unpublished doc.
  • Re-publish to sync. Folders don't auto-update on save. When you've added, edited, or deleted docs, hit Re-publish from the folder's hover card — removed files drop from the site automatically.

Readers get a clean docs layout with an "On this page" outline, a light/dark toggle, and your choice of viewer theme.

If a note references code in a repo with a GitHub remote, Grove turns those references into links to GitHub at the exact file and line. A mention like src/auth.ts:42, a bare filename, or a function name becomes a clickable link to the real code — resolved when you publish. (No GitHub remote, no links; the text is left as-is.)

Managing what you've published

Hover any published note or folder in the sidebar for its controls:

  • Copy — copy the share link again.
  • Re-publish (folders) — sync added, edited, and deleted docs.
  • Rotate — mint a new link and kill the old one (use this if a link leaked).
  • Unpublish — take it down entirely; the link 404s.

Published notes also get a small colored dot in the file tree and a pill in the editor header, so you can always see at a glance what's shared.

What your readers see

A clean, branded reading view of your doc — your title, your content, and a quiet "Made with Grove" footer. No app and no account required to read a link (unless the doc is gated). Published pages are read-only by design: the source of truth stays your local file in Grove.