Try DraftView on Any Public GitHub PR — No Account Required

The hardest part of adopting a new tool is the gap between reading about what it does and actually feeling whether it works for you. Sign up flows, empty states, and sample data all get in the way. We wanted to close that gap.

Starting today, draftview.app/try lets you paste any public GitHub PR URL and open it immediately. No account, no GitHub OAuth, no installation. If the PR touches Markdown, MDX, or AsciiDoc files, DraftView renders them and gives you the full review interface in seconds.

How It Works

Paste a URL like github.com/owner/repo/pull/123 into the input at the top of the page and press Try. DraftView fetches the PR directly from GitHub, renders every changed documentation file, and loads the review interface.

You get the same experience a signed-in user gets: rendered Markdown and AsciiDoc instead of raw diffs, inline commenting on any passage, and a file navigator that lets you jump between changed files. The only thing that differs from the full product is that your comments stay local to your browser session and are not synced back to GitHub — for that you need an account.

Works on any public repository. A few things to keep in mind: very large PRs are capped at the first 30 documentation files to keep load times reasonable, and files over 1 MB are skipped. Both are edge cases that rarely come up in practice.

What to Try It On

The best way to evaluate a review tool is on content you actually recognize. A few suggestions:

• An open PR from a project you contribute to or follow. The familiar context makes it easier to judge whether the rendering and commenting experience is better than GitHub's native diff view.
• A large documentation PR from a major open-source project. Projects like Docusaurus, OpenShift Docs, or Next.js have active documentation PRs that stress-test how well a tool handles real-world content.
• A PR that mixes code and docs changes. DraftView filters the file list to only show documentation files, so you see only what is relevant to the review without wading through unrelated code diffs.

Why This Matters for Documentation Teams

Convincing a team to adopt a new tool is easier when you can show it working on your actual content, not a demo repository. The share button in the top bar copies a link like draftview.app/try?pr=github.com/your-org/your-repo/pull/42 that anyone can open. No account required on their end either.

This makes it practical to share DraftView with your team before anyone has signed up. Open a recent documentation PR, click Share, and send the link in Slack. Your colleagues open it, see how their own documentation looks in a rendered review interface, and can make an informed decision about whether to adopt it for the team.

The same link works for external stakeholders — product managers, legal reviewers, or subject matter experts who currently receive exported Google Docs or PDFs. Show them a DraftView link on a real PR and the comparison becomes concrete.

From Try to Full Review

When you are ready to go beyond reading and commenting — to have comments flow back into GitHub as suggested changes and get sign-off from reviewers — the sign-up button is there. Accounts are free for public repositories. No credit card required.

The transition from the Try experience to a signed-in account is intentionally short. The same PR you were browsing anonymously becomes a fully tracked review with one click. Your team's existing GitHub workflow does not change; DraftView adds the rendered review layer on top of it.