nuartz was designed to publish Obsidian vaults as websites with zero friction. Drop your vault's content folder into content/ and nuartz handles the rest.
Supported OFM features
Wikilinks
Internal links using [[double brackets]] are resolved to the correct page URLs at build time. See Wikilinks for full syntax.
[[docs/getting-started]]
[[docs/getting-started|Custom label]]
[[docs/authoring-content#Frontmatter]]Image embeds
Embed images with the ! prefix, optionally specifying dimensions:
![[screenshot.png]]
![[screenshot.png|600x400]]Callouts
Obsidian-style callout blocks using the > [!type] syntax. See Callouts for all supported types.
> [!tip] My tip
> Content goes here.Tags
Inline #hashtag syntax in prose is recognised and linked to the tag index. Tags in frontmatter are also supported. See Tags.
Highlights
Wrap text in ==double equals== to highlight it:
This is ==highlighted== text.Comments
Obsidian comments (%%...%%) are stripped from the output — they never appear in the published site:
%% This comment is invisible to readers. %%Arrows
-> and <- are converted to proper typographic arrows (→ and ←):
Input -> Process -> OutputStrikethrough
Standard ~~strikethrough~~ syntax is supported.
Frontmatter compatibility
nuartz reads the same frontmatter fields as Obsidian (title, tags, aliases, date, draft, etc.). See Frontmatter for the full field reference.
Tips for a smooth migration
- Copy your vault's Markdown files into
content/. - Run
bun devand check the browser console for any broken wikilinks. - Pages with
draft: trueare excluded from listings but still accessible by URL in dev mode.
Some Obsidian features (Canvas files, Dataview queries, custom plugins) have no equivalent in nuartz. Plain Markdown notes and the OFM features listed above work out of the box.
Related
- Wikilinks — full wikilink syntax reference
- Callouts — callout types and nesting
- Tags — tag index and inline tags
- Authoring Content — full syntax guide