Publish RFCs and design docs to a URL

Your technical proposal is a markdown file. Publish it with one command and send the link to stakeholders for async review.

The problem with sharing proposals

Engineers write RFCs and design docs in markdown. Sharing them means importing into Confluence (loses formatting), converting to Google Docs (loses code blocks), or linking to a GitHub PR (requires repo access). The document exists as a .md file. Getting it to stakeholders shouldn't require a platform migration.

You could commit the RFC to a repo and link to it on GitHub. But not every reviewer has a GitHub account, and private repos lock out the people who need to read the doc most: product managers, leadership, external partners.

MDtoLink publishes markdown as-is. One command, one URL. No accounts required for readers.

How it works

1. Publish your proposal

mdtolink publish rfc-auth-redesign.md --slug rfc-auth

Your RFC is live at a clean URL. Send it to anyone who needs to review it.

2. Share the URL with reviewers

# Drop it in Slack, paste it in a Jira ticket, email it
https://mdtolink.com/@yourhandle/rfc-auth

Reviewers click and read. No login. No file downloads. Works on any device.

3. Update after feedback

# Edit your markdown file, then republish
mdtolink publish rfc-auth-redesign.md --slug rfc-auth

Same command, same URL. The content updates in place. No broken links.

Why use MDtoLink for technical proposals?

Any markdown file becomes a URL

RFCs, design docs, ADRs, tech specs. If it's markdown, it publishes.
No platform lock-in

Your source file stays in your repo, your editor, your workflow. MDtoLink is just the publishing layer.
Stable URL for linking in tickets

Reference the RFC from Jira, Linear, or GitHub issues. The link stays valid even after the proposal is revised.
Custom domain for internal branding

On the Publisher plan, host proposals at rfcs.yourcompany.com.

Frequently Asked Questions

Can I update an RFC after publishing it?

Yes. Run mdtolink publish with the same file and slug again. The content updates in place. The URL stays the same, so any links in tickets or Slack threads still work.

Do reviewers need an account to read the proposal?

No. Published documents are accessible to anyone with the link. No login, no sign-up. Just open the URL and read.

Can I use a custom domain for internal proposals?

Yes, on the Publisher plan. Point a CNAME record to mdtolink.com and host proposals at something like rfcs.yourcompany.com. SSL is automatic.

Does MDtoLink render code blocks and diagrams in proposals?

MDtoLink renders full markdown including fenced code blocks with syntax highlighting, tables, headings, lists, and inline code. If your markdown renders on GitHub, it renders on MDtoLink.

Publish your next RFC in 30 seconds

Free to start. No credit card required.

Start Publishing Free Read the Docs

See all use cases for MDtoLink.