Publish
Turn a vault into a website.
Choose notes, choose a theme, and Neoma writes a static site to a folder on your device. Host it anywhere that serves files, or open it straight from disk.
How it works
- vault/the notes you choose
- Publishrendered on your device
- _site/index.htmlstatic files
- any hostor straight from disk
What you get
Static output.Built locally. Host it anywhere.
- The same renderer as the editor. Maths, callouts, code, tables and embeds look the way you wrote them.
- Links that work. Wiki links become relative links between published pages.
- Search and graph. Optional, from a script of about 5 KB.
- Four themes. Neoma, Paper, Minimal and Terminal, each light and dark.
- SEO files. Page descriptions and robots.txt, plus a sitemap when you give the site's address.
$ tree _site _site/ ├── index.html ├── transformers.html ├── neural-networks.html ├── sources.html ├── graph.html ├── search-index.json ├── sitemap.xml ├── robots.txt ├── site.json ├── assets/ │ ├── site.css │ ├── site.js # about 5 KB │ └── search.js └── files/ └── attention.pdf
Privacy
Nothing is uploaded by Neoma.
Publishing builds files on your device. Where they go next is up to you: a folder, a USB stick, GitHub Pages, your university's web space, any static host.
- Only what you select. Neoma reads just the notes you chose to publish.
- Private links stay private. A link to an unpublished note renders as plain text.
- Only the files you use. Attachments are copied only if a published page shows them.
- No vault paths. Your folder structure is never written into the site.
-
Opt out per note.
publish: falsein a note's properties keeps it out, always.
Proof
These docs are a published vault.
Every page under /docs is a Markdown note in the repository, built by the same publishing renderer you use in the app.