Skip to main content

📝 Lesson 7.3: Publishing & Sharing Your Notes

A second brain doesn't have to stay locked in your head. Some of your best notes want to be read — as a public "digital garden," a documentation site, a blog, or just a link you send a colleague. In this lesson we survey every way to get notes out of Obsidian and onto the web, from the one-click official service to free static sites — and how to keep your private notes private while you do it.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Name real reasons to publish and match each to the right tool
  • Describe Obsidian Publish and its free alternatives — Quartz, the Digital Garden plugin, exports, GitHub Pages, and Netlify
  • Use frontmatter flags (like publish: true) to control exactly which notes go public
  • Anticipate the gotchas — private content, broken links, and images — before you hit publish

⏱️ Estimated Time: 50 minutes

🎯 Project: Choose a publishing approach and actually publish (or cleanly export) one note or a small set.

In This Lesson

Why Publish at All?

Publishing isn't for everyone, and that's fine — plenty of vaults stay gloriously private forever. But there are genuinely good reasons to share, and knowing which reason is yours points you straight at the right tool:

  • A digital garden — a public, ever-growing web of your linked notes that others (and future-you) can wander. Learning in the open; ideas cross-pollinating.
  • Documentation — a project handbook, a team wiki, an API guide, a course. Notes are a great source; the web is a great destination.
  • A blog — write in Obsidian where your thinking lives, publish selected posts without ever leaving your editor.
  • Sharing with a person — send one collaborator a clean, readable link instead of a raw .md file.

🧠 Mindset

Publishing can feel like it demands perfection — a polished site, finished essays, nothing embarrassing. It doesn't. The "digital garden" idea exists precisely to lower that bar: gardens have seedlings and half-grown ideas, not just show-flowers. Publishing a rough, honest note that helps one person beats a perfect draft that never ships. Start small, mark things as "growing," and let it evolve in public.

graph TD A["📝 Your vault"] --> Q{"How do you
want to share?"} Q -->|"One-click, official,
graph & links preserved"| B["🌐 Obsidian Publish
(paid)"] Q -->|"Free full site,
tech-comfortable"| C["🌱 Quartz / Digital Garden
→ GitHub Pages / Netlify"] Q -->|"Just one file
or a handout"| D["📄 Export to
HTML / PDF / Markdown"] B --> E["🔗 A public link"] C --> E D --> F["📎 A file to send"]

Obsidian Publish (Official)

Obsidian Publish is the company's paid publishing service, and it's the smoothest route by far. From inside Obsidian you pick exactly which notes to publish, click Publish, and they go live on the web at a public URL — no build tools, no servers, no code.

What makes it special is how faithfully it recreates the Obsidian experience for your readers:

  • Handles your [[wikilinks]]. Internal links become working web links automatically — no rewriting.
  • Publishes the graph. Readers can see and navigate the interactive graph of your published notes.
  • Selective by design. You choose note-by-note what's public; the rest of your vault stays private.
  • Custom domain & appearance. Point your own domain at it and adjust the look; you can even password-protect a site.
  • Backlinks, search, page preview — the reading experience feels like Obsidian.

The trade-off is simply that it's a subscription. If you want the least-friction path, value the preserved links and graph, and would rather pay than maintain a site, Obsidian Publish is the obvious pick — and it supports the developers. (This very course site you're reading, by contrast, is plain static HTML — a reminder that Publish is one option among several, not the only way.)

✅ Pro Tip

Publish and Sync are separate paid services and separate ideas. Sync is private, for your devices; Publish is public, for your readers. You can use either without the other. Don't confuse "my notes are synced" with "my notes are published" — nothing is public until you explicitly publish it.

Free & Alternative Routes

Prefer to spend time instead of money, or want full control over the output? The Obsidian community has built excellent free paths. They ask a little more setup, but they're powerful and yours.

Tool What it is Best for
Quartz A free, open-source static-site generator built specifically to turn an Obsidian vault into a fast website — it understands wikilinks, backlinks, and graphs. A full digital garden you host free on GitHub Pages or Netlify.
Digital Garden (community plugin) An Obsidian plugin that publishes flagged notes to a template site (deployed on a host like Netlify/Vercel), controlled from inside Obsidian. A Publish-like experience without the subscription, driven by frontmatter flags.
Export to Markdown / HTML / PDF Save one note (or a folder) as a portable file — built-in "Export to PDF," or community exporters for clean HTML/Markdown. Sending a single document to someone who doesn't use Obsidian.
GitHub Pages Free static hosting straight from a GitHub repo. Quartz and many generators deploy here. Hosting a generated site free, with version control built in.
Netlify Free static hosting with drag-and-drop deploys or automatic builds from a repo, plus custom domains. The simplest "here's a folder, give me a URL" hosting — including drag-and-drop.

The typical free pipeline looks like this: Obsidian vault → a generator (Quartz or Digital Garden) → a host (GitHub Pages or Netlify) → your public URL. You write in Obsidian as always; the generator converts your Markdown and links into a real website; the host serves it to the world for free.

💡 A note on this course site

The pages you're reading right now are exactly this idea taken to its simplest form: hand-written static HTML, deployable to Netlify by dragging the folder into its dashboard. You don't even need a fancy generator to share knowledge on the web — a folder of HTML and a free host is a complete, durable publishing stack. Ray's other courses ship the same way.

⚠️ Important Note: The free routes generally build a separate public copy of the notes you choose — your private vault stays on your machine untouched. Publishing never "uploads your whole vault" unless you tell it to. You always decide what crosses the line into public.

Exporting Individual Notes

Not everything needs a website. Often you just want to hand someone one readable document. Obsidian and its ecosystem make that easy:

  • Export to PDF is built in — open the command palette (Ctrl/Cmd+P) and run "Export to PDF," or use the note's "More options" menu. Great for a polished handout, a résumé, or a report.
  • Copy as plain Markdown — since notes are Markdown, you can just send the .md file; anyone can read it in any editor, and GitHub/GitLab render it beautifully.
  • Export to HTML — community exporter plugins produce a standalone HTML file (styles baked in) you can email or drop on any host.

⚠️ Watch Out

When you export a single note that contains [[wikilinks]] to other notes, those links may point nowhere in the exported file — the reader doesn't have your vault. For standalone documents, either avoid internal links, or export the small set of linked notes together with a tool that rewrites the links. Always open your export and read it as your recipient will before sending.

What to Keep Private (Frontmatter Flags)

This is the part to get right before you publish anything. Your vault almost certainly holds things you'd never want public — journal entries, passwords, half-baked opinions, other people's information. The good news: every serious publishing tool is opt-in per note, and the cleanest way to control it is a frontmatter flag.

You met YAML frontmatter (properties) earlier in the course — the --- block at the very top of a note. Publishing tools read a flag there to decide a note's fate. The common convention:

---
title: How I Take Meeting Notes
publish: true
tags: [workflow, notes]
---

The body of a note I *am* happy to share...

Only notes with publish: true go out; everything else is ignored. Different tools use slightly different keys — Obsidian Publish maintains its own list of chosen files, the Digital Garden plugin looks for a flag like dg-publish: true, and Quartz can be configured to respect a publish or draft field. The principle is universal:

📖 Definition

Publish flag: a boolean in a note's frontmatter (commonly publish: true) that a publishing tool uses to include or exclude that note from the public site. Because it's opt-in, a note is private by default and only becomes public when you deliberately flip the flag. Treat that flag as a lock: the safe default is "off."

⚠️ Watch Out — the whole-folder trap

Some setups publish an entire folder rather than flag-by-flag. That's convenient but dangerous: drop a private note in the wrong folder and it goes live. Whichever model you use, do a dry-run and look at the list of what will be published before you confirm. When in doubt, keep a dedicated Published/ folder and put only vetted notes in it.

Gotchas: Links & Images

Two things break most first-time published sites. Handle them up front and your launch will be smooth.

🔗 Broken links

If Note A links to Note B with [[Note B]], but you only publish Note A, the link on your site points at a page that doesn't exist. Publishing tools handle this differently — Obsidian Publish and Quartz gracefully turn links to unpublished notes into plain text or a "not published" state — but you should still check your published pages for dead links. Rule of thumb: if you publish a note, publish the notes it links to, or accept those links will be inert.

🖼️ Images and attachments

Embedded images (![[diagram.png]]) must be published alongside the notes that use them, or they'll show as broken. Most tools include referenced attachments automatically, but large media can slow a site or blow past free hosting limits. Keep images reasonably sized, and confirm they actually load on the live site — not just in your local vault.

✅ Pro Tip — the pre-flight checklist

Before you announce a published site, open it in a private/incognito browser window (so you're not fooled by your own cache or login) and click around as a stranger would. Check: Do internal links work? Do images load? Is anything showing that should be private? Does it read well on a phone? Five minutes of this catches nearly every embarrassing bug.

⚠️ Important Note: "Unpublishing" is not the same as "deleting from the internet." Once a page has been public, it may be cached, screenshotted, or archived. Never publish anything you'd be harmed by later — the safest privacy control is not putting it online in the first place.

🎯 Project: Publish One Note

Theory's done — let's actually ship something small and real. The goal is to get one note (or a tiny set) out of your vault and into a shareable form, whichever route fits you. Small and finished beats big and stalled.

🏋️ Choose a route and publish or export

Objective: End with a link or a file you could genuinely send to another person.

Instructions (about 25 minutes):

  1. (3 min) Pick one note you're comfortable sharing — a how-to, a book summary, a recipe. Read it once to be sure nothing private hides inside.
  2. (2 min) Add clean frontmatter, including publish: true and a real title:, so it's ready for any flag-based tool.
  3. (15 min) Choose your route and do it:
    • Quickest — Export: Run "Export to PDF" (or export to HTML) and open the result. You now have a file to send. Done.
    • Free web — Netlify drag-and-drop: Export the note to an HTML file, put it in a folder, and drag that folder onto Netlify Drop to get an instant public URL.
    • Full garden — Quartz / Digital Garden: If you're tech-comfortable, follow the tool's quick-start to build your flagged notes into a site and deploy to GitHub Pages or Netlify. (Budget more than 15 minutes the first time — that's fine.)
    • Official — Obsidian Publish: If you have it, select the note and click Publish.
  4. (3 min) Open the result as a stranger (incognito window, or on your phone). Verify links, images, and that nothing private leaked.
  5. (2 min) Send the link or file to yourself (or a friend) — proof it truly works for someone who isn't you.
💡 Hint — the lowest-effort win

Not ready for a whole site? "Export to PDF" on a single tidy note gives you a shareable artifact in under two minutes, and it teaches you what your notes look like outside Obsidian — which is the real lesson here. Upgrade to a hosted garden later, once you know you enjoy sharing.

✅ Solution — a publish-ready note skeleton 
---
title: My First Published Note
publish: true
created: 2026-09-14
tags: [public, howto]
---

# My First Published Note

A short, self-contained piece of writing with **no private details**,
whose internal links either point to other published notes or are
removed for this standalone version.

![[a-small-image.png]]  <!-- make sure this image gets published too -->

Keep it self-contained: no links to private notes, images small, nothing you'd regret. That's a note that publishes cleanly by any route.

✅ Project Completion Checklist

  • You chose one note and confirmed it holds nothing private
  • It has clean frontmatter with a publish: true flag and title
  • You produced a real output — a public link or an exported file
  • You viewed it as a stranger (incognito or another device) and links/images work
  • You successfully shared it with at least one recipient (even just yourself)

🎯 Quick Quiz

Question 1: Which frontmatter line is the common convention for marking a note to be published?

Question 2: You want a full, free digital garden hosted on the web. Which combination fits?

Best Practices for Publishing

✅ Do's

  • Publish opt-in. Use a publish: true flag so notes are private by default.
  • Preview as a stranger. Incognito window or another device before you announce anything.
  • Match the tool to the goal — a file to send? Export. A garden? Quartz/Publish.
  • Publish linked notes together, or accept those links will be inert.

❌ Don'ts

  • Don't publish whole folders blindly — one stray private note goes live with them.
  • Don't assume unpublishing erases a page — the web caches and archives.
  • Don't ship broken images — confirm attachments load on the live site.
  • Don't wait for perfect. A useful rough note beats a flawless one you never share.

📓 Learning Journal

Open your Learning Journal note in your vault. After this lesson, jot down:

  • Key concepts you learned
  • Techniques that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and feelings about learning this

✍️ This lesson's prompt: Is there a version of your notes you'd want the world (or one person) to see? Name one note or topic you'd happily share, and one you'd never publish — what's the real difference between them, and does that tell you where your privacy line sits?

📝 Lesson Summary

🎓 Key Takeaways

  • People publish for four main reasons: a digital garden, documentation, a blog, or sharing with a person — pick the tool that fits the goal.
  • Obsidian Publish is the paid one-click route that preserves links and the graph; free routes include Quartz, the Digital Garden plugin, and plain exports.
  • Host free with GitHub Pages or Netlify (drag-and-drop). This very course is static HTML on Netlify — proof that simple works.
  • Control what's public with a publish: true frontmatter flag, and always check broken links and images as a stranger before you share.

🎉 What You've Accomplished

You've learned every practical way to get a note out of your vault and in front of a reader — from a two-minute PDF to a full public garden — and, just as importantly, how to keep the private stuff private while you do it. You published or exported something real. Your second brain can now speak to the world on your terms.

❓ Common Questions at This Stage

Is Obsidian Publish worth paying for when Quartz is free?

It depends on how you value your time. Obsidian Publish is near-zero setup, preserves links and the graph automatically, and supports the developers — great if you want to write, not maintain. Quartz and the Digital Garden plugin cost nothing but ask for some technical setup and upkeep. Both produce lovely sites; choose by budget and how much tinkering you enjoy.

Can I use my own domain name?

Yes, across the board. Obsidian Publish supports custom domains, and hosts like Netlify and GitHub Pages let you point your own domain at a generated site. You're never stuck on someone else's URL.

What if I only want to share with one specific person, privately?

For a single reader, an export (PDF or a shared Markdown/HTML file) is often simplest and keeps nothing on the open web. If you need a private site, Obsidian Publish offers password protection, and some hosts support access controls — but remember any "public" URL can be shared onward, so match the method to how sensitive the content is.

🔭 Looking Ahead

Your notes are now safe, connected, task-aware, and shareable. Next we make them travel with you: the final serious-workflow skill is mastering Obsidian across mobile and multiple devices — capturing on your phone, reading on a tablet, and keeping everything in graceful sync.

✅ Before the Next Lesson

  • Keep the note (or link) you published — you may extend it later
  • Decide your privacy line: which folders or flags mean "never public"
  • Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

You just crossed a line most note-takers never do: you turned a private thought into something you could hand another human being. That's knowledge doing what it's for. Share generously, keep the private things private, and let your garden grow. 🔮