Why another Obsidian publisher?
Quartz proved that publishing Obsidian vaults as websites works. It's a great tool. But Quartz is a static site generator with its own templating system — when you want to change the UI beyond what the theme allows, you're fighting the tool instead of building with it.
Nuartz takes a different bet: what if the "Obsidian to website" pipeline was just a library, and the site was a normal Next.js app?
That means you get React components, shadcn/ui, Tailwind CSS, the entire npm ecosystem, and every Next.js feature — server components, ISR, API routes, middleware. No custom templating language, no plugin API to learn. If you know Next.js, you already know how to customise Nuartz.
Two layers
Nuartz is split into a library and a starter template:
nuartz(npm package) — the data layer. Parses Obsidian markdown, resolves wikilinks, builds backlink graphs, generates search indices. Ships zero UI. You canbun add nuartzand wire it into any Next.js app.apps/web(starter template) — a complete Next.js 15 app using shadcn/ui. Sidebar, graph view, search, dark mode, OG images, comments — all included. Clone it, drop in your markdown, deploy.
Most people start with the starter template and customise from there. If you have an existing Next.js app (portfolio, blog, docs site), install the package and integrate only what you need.
Deploy anywhere
Nuartz supports two deployment modes:
GitHub Pages (static) — all pages are pre-built as HTML. Free hosting, no server. Search, graph view, popover previews, dark mode — all work. The prebuild script generates static JSON files so features that would normally need API routes work without a server.
Vercel / Netlify (server) — full feature set. Dynamic OG images (each page gets its own social preview card), external link previews on hover, and Next.js image optimization. The free tier on Vercel is generous enough for most personal sites.
Both modes share the same codebase. You don't need to change your code to switch — just toggle output: "export" in next.config.ts. See Hosting for details.
Who is this for?
Obsidian users who know some React — or want to learn. Nuartz doesn't hide complexity behind abstractions. It exposes a straightforward Next.js app that you can read, understand, and modify.
Next.js developers who write in Obsidian — if you already have a Next.js project and want to add a blog or knowledge base with Obsidian compatibility, bun add nuartz is all you need.
People who outgrew their SSG — if you've hit the ceiling of Hugo, Jekyll, or Quartz's customisation and wish you could just use React, Nuartz is that option.
Quartz vs Nuartz
| Quartz | Nuartz (package) | Nuartz (starter) | |
|---|---|---|---|
| Type | SSG (fork & deploy) | npm library | Next.js app (clone & deploy) |
| UI | Built-in theme | None — bring your own | shadcn/ui included |
| GitHub Pages | Supported | Supported | Supported (static export) |
| Customisation | Plugin API | Any React component | Modify components directly |
Choose Quartz for a quick, opinionated setup. Choose Nuartz when you want full control over your site's UI and behaviour.