A wiki made of markdown files and URLs

Publish markdown files as a lightweight internal wiki. Each doc gets its own URL. Link between them for navigation.

Most wiki tools are overkill

Confluence and Notion are full platforms. Per-user pricing, permission systems, WYSIWYG editors, template galleries, integrations marketplace. For a 5-person team with 20 docs, that's a lot of overhead for what amounts to "I need people to read some pages."

Markdown files in a repo are the other extreme. Great for developers who have repo access, but useless for anyone who doesn't: new hires, non-technical team members, external partners.

MDtoLink sits in the middle. Keep your docs as markdown files (in a repo, in a folder, wherever). Publish each one to a URL. Link between them. That's your wiki.

How it works

1. Organize docs in a folder

wiki/
  getting-started.md
  architecture.md
  deploy-guide.md
  coding-standards.md
  incident-response.md

Standard markdown files. Keep them in a repo or a shared folder. Structure them however makes sense for your team.

2. Publish each file

mdtolink publish wiki/getting-started.md --slug wiki-getting-started
mdtolink publish wiki/architecture.md --slug wiki-architecture
mdtolink publish wiki/deploy-guide.md --slug wiki-deploy-guide
mdtolink publish wiki/coding-standards.md --slug wiki-coding-standards
mdtolink publish wiki/incident-response.md --slug wiki-incident-response

Each doc gets its own URL. Automate this in a script or CI pipeline to publish all docs at once.

3. Link between docs

# Getting Started

Welcome to the team. Here's what you need to know.

## First Steps
1. Read the [architecture overview](https://wiki.yourcompany.com/wiki-architecture)
2. Follow the [deploy guide](https://wiki.yourcompany.com/wiki-deploy-guide)
3. Review our [coding standards](https://wiki.yourcompany.com/wiki-coding-standards)

Use standard markdown links to reference other docs. With a custom domain, the URLs feel like a real wiki.

Why use MDtoLink as a wiki?

No per-user pricing

Pay for the plan, not for readers. Published pages are accessible to anyone with the link. Ten readers or ten thousand, same price.
Each doc is a standalone URL

Share individual pages. Bookmark specific docs. Link to them from Slack, email, or other tools.
Readers don't need accounts

No Confluence license, no Notion invite. Anyone with the URL can read. Reduces onboarding friction for new team members.
Custom domain for a branded wiki

On the Publisher plan, host your wiki at wiki.yourcompany.com. Looks professional. Feels internal.

Frequently Asked Questions

Can I link between published docs?

Yes. Each published doc has its own URL. Use standard markdown links to reference other docs. With a custom domain, links look like wiki.yourcompany.com/getting-started and wiki.yourcompany.com/deploy-guide.

Is there per-user pricing?

No. MDtoLink pricing is per account, not per reader. The Publisher plan ($18/mo) includes up to 5 team members who can publish. Readers don't need accounts at all.

Can I use a custom domain for the wiki?

Yes, on the Publisher plan. Point a CNAME record for something like wiki.yourcompany.com to mdtolink.com. SSL is automatic. All your docs live under one branded domain.

How do I keep the wiki up to date?

Keep the source markdown files in your repo. Changes go through pull requests. Publish in CI on every merge so the live docs always match the repo. No manual syncing needed. See our documentation use case for more on this workflow.

Start your wiki in minutes

Free to start. No credit card required.

Start Publishing Free Read the Docs

For full docs sites, see Documentation. Or browse all use cases.