Welcome to mdshare
This page is a live sample. It’s a single markdown file on Felix’s Mac, published to a web link without leaving the vault it lives in.
The point of the tool is narrow: take one markdown doc, give it a clean address someone can open on their phone, and keep everything else private. No login for the reader, no app to install, no copy-paste into Google Docs.
How a doc gets here
You add its path to an allowlist, and the build renders only that file. Nothing else on the disk is reachable — the build script never looks past the files you named. That’s the whole safety model, and it’s enforced by construction, not by a setting you have to remember.
A doc can be public (anyone with the link), share-gated (reachable only through a private /s/<token>/ link), or password-protected (the link plus a password). This page is public.
Anything with personal, legal, or health detail stays off this lane. Those live on an encrypted, self-hosted setup instead.
What renders
Standard markdown, plus the Obsidian pieces that show up in real notes:
- Callouts (the two boxes above)
- Tables, with sensible column behaviour on a narrow screen
- Task lists
- Code blocks
- Wikilinks, when they point at another published doc
A table
| Tier | Reader needs | Good for |
|---|---|---|
| Public | just the link | a note you don’t mind anyone reading |
| Share | the /s/… link |
a client, a family member |
| Password | link + password | the same, but semi-private |
A checklist
A little code
// the entire allowlist, conceptually
for (const doc of config.docs) publish(doc);
Reading on
When a wikilink points at a doc that hasn’t been published, it shows as plain text rather than a dead link — so it never leaks the name of something you’re still keeping private.
That’s it. Add a doc, send the link.