Project handoffs that don't get lost

Publish handoff documentation to a permanent URL. It stays accessible after team members move on or lose repo access.

Context evaporates when people leave

When a developer leaves a project, context evaporates. The architecture decisions, the workarounds, the "why we did it this way" knowledge that lives in their head walks out the door.

Handoff docs in a repo work only if the next person has repo access. Docs in Slack get buried under months of messages. Docs in Confluence require a license. A Google Doc might work, but then you're maintaining documents in a tool disconnected from the codebase.

A published URL stays accessible regardless of team changes. Pin it in a channel, bookmark it, link it from the project's README. It's always there.

How it works

1. Write the handoff doc

# Project Handoff: Payments Service

## Architecture
- Express API on port 3000, PostgreSQL for state
- Stripe webhooks handled in /src/webhooks/stripe.ts
- Retry logic uses exponential backoff (see /src/lib/retry.ts)

## Known Issues
- Webhook dedup fails on concurrent requests (ticket PAY-312)
- Test suite takes 4 min; mock Stripe responses to speed up

## Setup
1. Clone the repo
2. Copy .env.example to .env
3. Run `docker compose up` for PostgreSQL
4. Run `pnpm dev`

## Key Contacts
- @sarah for Stripe account access
- @mike for production deploy permissions

Include architecture decisions, setup instructions, known issues, and key contacts. The stuff that matters when someone new picks up the project.

2. Publish to a permanent URL

mdtolink publish handoff.md --slug project-handoff

The handoff doc is now accessible at a stable URL. No repo access needed to read it.

3. Pin the URL where the team will find it

# In your project README
## Handoff Documentation
https://mdtolink.com/@yourhandle/project-handoff

# Or pin it in the team Slack channel

Link it from the README, pin it in Slack, add it to the project wiki. The URL is permanent.

Why use MDtoLink for project handoffs?

Permanent URL survives team changes

People leave. Repo access gets revoked. The handoff URL keeps working.
No repo access needed to read

Contractors, new hires, stakeholders from other teams: anyone with the link can read the doc.
Update in place

The new team can update the handoff doc as they learn the project. Same URL, updated content.
Searchable by anyone with the link

Published pages are rendered HTML. Readers can Ctrl+F to find what they need. No clunky wiki search.

Frequently Asked Questions

Does the handoff doc stay accessible after the author leaves?

Yes. Published documents live at their URL regardless of who published them. If the author's MDtoLink account is active (or on a team plan), the URL remains accessible.

Can I update a handoff doc after publishing?

Yes. Run mdtolink publish with the same slug and the content updates in place. The URL stays the same. This is useful when the incoming team adds their own notes.

Do readers need repo access to view the handoff doc?

No. That's the point. Published pages are accessible to anyone with the link. No GitHub access, no VPN, no special permissions.

Can I publish multiple handoff docs for different projects?

Yes. Each document gets its own slug and URL. Publish as many as you need: mdtolink publish handoff-api.md --slug handoff-api and mdtolink publish handoff-frontend.md --slug handoff-frontend.

Publish your handoff doc in 30 seconds

Free to start. No credit card required.

Start Publishing Free Read the Docs

See all use cases for MDtoLink.