Meadow Notes: Turn Markdown into a Microsite — Hands-On 2026

A new tool called Meadow Notes (meadow-notes.com) is generating buzz in the Markdown publishing space. The concept is simple but powerful: write interconnected Markdown notes in a folder structure, and Meadow Notes turns the whole collection into a shareable microsite with a knowledge graph that readers can explore.

This is not your typical "Markdown to HTML" converter. Meadow Notes treats your note-taking database as a publishing asset rather than a private archive. It targets a specific gap between private note-taking (Obsidian, Logseq) and public publishing (blog, newsletter) — the idea that your notes, when organized well, are already a publishable product.

I spent a day building a small microsite with Meadow Notes. Here is the full hands-on review, compared with md2rich and traditional Markdown publishing workflows.

1. What Meadow Notes Does

Meadow Notes works as both a note-taking environment and a publishing platform. You create folders and Markdown files in their editor, link notes together with [[wiki-links]] (borrowed from Obsidian and Roam Research), and Meadow Notes renders the whole structure as a static website. Each note becomes a page, each link becomes a navigable connection, and the knowledge graph visualization becomes the site's navigation map.

Key capabilities:

• Folder-as-navigation: Your folder hierarchy maps directly to site navigation
• Backlinks rendered as reverse-references: Every note shows what links to it
• Graph view: An interactive network map of all connected notes
• Static site export: Publishes as plain HTML/CSS/JS — no runtime database
• Custom domain support: Host on your own domain

The resulting microsite feels like a mix between a digital garden (like Gwern or Andy Matuschak's notes) and a feature-rich wiki. For researchers, writers, and knowledge workers who already maintain an Obsidian vault or a folder of Markdown files, Meadow Notes offers a one-click path from private notes to public knowledge base.

2. Hands-On: Setting Up a Microsite

I created a Meadow Notes account and imported a folder of 12 Markdown files about "Markdown publishing workflows." The import process was straightforward — drag and drop a zip of Markdown files:

my-markdown-publishing/
  index.md
  guides/
    linkedin-publishing.md
    x-articles-workflow.md
    medium-conversion.md
  tools/
    md2rich-review.md
    pandoc-workflow.md
    obsidian-vs-logseq.md
  comparisons/
    client-side-vs-cloud.md
    static-site-vs-cms.md

Each [[wiki-link]] reference was automatically recognized. Meadow Notes even detected orphaned notes (files no other note links to) and flagged them as a suggestion to add links or remove them.

The resulting microsite had:

• A homepage summarizing the content tree
• Individual pages for each Markdown file
• Backlinks section at the bottom of every page
• Full-text search across all notes
• A "graph explorer" showing how all 12 files connected

What worked well: The graph navigation is genuinely useful for browsing. For a collection of 12 interconnected notes, it felt more discoverable than a traditional blog archive. The static site export was fast and clean.

What felt constrained: Custom styling is limited to preset themes. You cannot inject custom CSS or JavaScript. For users who want pixel-perfect control over their site's appearance, this is a limitation. The graph view is the primary navigation metaphor — if readers prefer a chronological blog layout, Meadow Notes doesn't offer that option.

3. Where Meadow Notes Fits in the Markdown Ecosystem

There are now several ways to publish Markdown content online. Each serves a different use case:

Meadow Notes occupies a unique niche: the "publishable knowledge base." It is not a replacement for a blog and not a replacement for a rich text converter. It is a third category — a public-facing, explorable collection of notes.

4. The md2rich Complement: Cross-Posting Individual Articles

This is where the two tools fit together. If you build a Meadow Notes microsite for your knowledge base, you will have dozens of well-written Markdown notes — but they are trapped inside the microsite's graph format. To cross-post individual articles to LinkedIn, X Articles, or Medium, you need a rich text converter.

md2rich solves that exact problem:

1. Open your Meadow Notes page in Markdown format
2. Copy the Markdown content
3. Paste it into md2rich.com
4. Copy the rendered rich text
5. Paste directly into LinkedIn, X Articles, or Medium

The beauty of this workflow is that your knowledge base stays in Meadow Notes (with graph navigation, backlinks, and full-text search), while your social distribution goes through md2rich. You get the best of both tools without compromising on either.

And because md2rich runs 100% in your browser, no data ever leaves your machine. You are not uploading your notes to a second platform just to get them out of the first one.

Example: Converting a Meadow Notes Article for LinkedIn

Here is a Markdown excerpt from a Meadow Notes page about client-side converting:

## Why Client-Side Conversion Matters

Most Markdown-to-rich-text tools send your content to a server for processing.
This means:

- **Privacy risk**: your draft is stored on someone else's infrastructure
- **Speed dependency**: conversion waits on network round-trips
- **Service availability**: if the server goes down, your tool stops working

A client-side tool like md2rich avoids all three problems.\
It runs in your browser using JavaScript.\
Your Markdown never touches a network.

Paste this into md2rich.com, click "Copy Rich Text," and paste into LinkedIn. The headings, bold text, and list formatting all carry over with correct styling. The entire conversion takes under a second and uses zero server resources.

5. Privacy Comparison: Microsite Hosting vs Client-Side

Meadow Notes hosts your content on their servers (cloud upload required). This enables features like global graph view and full-text search across all notes. The trade-off is that your content leaves your machine.

md2rich takes the opposite approach: everything stays in the browser. There is no server, no upload, no storage. The trade-off is that md2rich does not offer a persistent publishing home — it is a conversion tool, not a hosting platform.

Which one is right depends on your content. Public knowledge base content (e.g., tutorials, reference guides) benefits from Meadow Notes' discoverable graph format. Drafts, sensitive writing, or client work is better handled by a purely client-side pipeline: write in a local Markdown editor, convert with md2rich, paste to the target platform. No cloud upload anywhere in the chain.

For maximum privacy, use both: publish public-facing reference material in Meadow Notes, and use md2rich to individually distribute high-value articles to social platforms without any cloud intermediary.

6. Who Should Use Meadow Notes

Meadow Notes is ideal if you:

• Already maintain a Markdown-based knowledge base or Obsidian vault
• Want a public-facing version of your notes without building a custom site
• Believe your notes are valuable as a knowledge graph, not just individual articles
• Are comfortable with cloud uploads for discoverable public content

Stick with traditional workflows if you:

• Publish individual articles to social platforms rather than hosting a note collection
• Need pixel-perfect control over site styling
• Handle sensitive or client-confidential content that should never leave your machine
• Prefer a chronological blog layout over a graph navigation

7. Conclusion

Meadow Notes is a genuinely new product category: a publishing platform for your note-taking database. It repositions the folder of Markdown files from "private notes" to "publishable knowledge base" with minimal effort. The graph-based navigation is a meaningful improvement over traditional blog archives for interconnected topics.

It does not replace the need for a cross-platform rich text converter. When you want to take individual articles from your microsite and distribute them to LinkedIn, X Articles, or Medium, md2rich is the natural complement — zero-upload, zero-registration, one-click conversion.

The broader trend here is worth noting: Markdown is becoming the lingua franca of online publishing, not just a format for developers. Tools like Meadow Notes, Obsidian Publish, and md2rich all solve different parts of the publishing funnel, and they work better together than alone.

Try md2rich: open the editor, paste Markdown, copy rich text. Free, client-side, open-source. No upload needed.