Exporting and sharing notes

There’s no separate bundler command — lettuce publish is the export path. It renders the vault to a self-contained static site (HTML, search, graph, tag pages, sitemap) with no .lettuce/ cruft, which is exactly what you share or host.

What gets exported

By default, only notes with published: true in their frontmatter are rendered — so marking the handful of notes you want to share is the selection mechanism (there’s no folder include/exclude config). Pass --all to render every note instead.

lettuce publish ~/Notes --out ~/share/site          # only published: true notes
lettuce publish ~/Notes --out ~/share/site --all     # everything

See CLI cookbook/03 lettuce publish for the full flag set, and Publishing/01 Overview for how the static site is built.

Sharing privately vs publicly

• Keep something out of the export: simply don’t set published: true on it (or don’t use --all). Notes default to unpublished.

• A clean public mirror: keep sensitive notes in one vault and the shareable ones in another, and publish the public vault. There’s no in-place frontmatter-stripping flag — strip or pseudonymise content in the note itself before marking it published: true.

• Host it: lettuce deploy builds and pushes the same site to GitHub Pages — see CLI cookbook/04 lettuce deploy.

Single file

To export one note as a standalone HTML page (no site), use CLI cookbook/02 lettuce render:

lettuce render Notes/Recipe.md --out recipe.html

Related

• CLI cookbook/03 lettuce publish — build the static site

• CLI cookbook/04 lettuce deploy — push it to GitHub Pages

• CLI cookbook/02 lettuce render — one Markdown file → one HTML page