Question 1

Do my reviewers need a GitHub account to use DraftView?

Accepted Answer

Unfortunately, yes. Because GitHub's policy does not allow suggestions and comments on behalf of unauthenticated users, all reviewers must sign in with a GitHub account. For public repositories, anyone with a GitHub account can review and comment. For private repositories, reviewers must also have access rights to the repository.

Question 2

Which documentation formats does DraftView support?

Accepted Answer

DraftView currently supports MDX, AsciiDoc, standard Markdown, and is planning support for RST formats.

Question 3

Can I use DraftView with private GitHub repositories?

Accepted Answer

Yes, DraftView is designed to work seamlessly with both public and private repositories. You can connect your private repos securely, and only authorized reviewers will have access to the visual review sessions.

Question 4

Is my data secure with DraftView?

Accepted Answer

Yes, all data is encrypted at rest and in transit. DraftView follows industry best practices for security and compliance, including SOC2 readiness. Your documentation and review sessions are protected with enterprise-grade security measures.

Question 5

What documentation platforms work with DraftView?

Accepted Answer

DraftView integrates with GitHub, so as long as your documentation is in a GitHub repository, you can use the visual review engine. This includes Docusaurus, GitBook, Redocly, ReadMe, Hugo, MkDocs, and any other docs-as-code platform.

Question 6

How does DraftView's visual review interface work?

Accepted Answer

DraftView uses a proprietary Diff-Core engine to render your documentation changes. It provides a clean, visual representation of modifications, like reviewing a Google Doc, making it easier for non-technical stakeholders to review and suggest edits without seeing raw Markdown diffs.

Question 7

Is there a free tier or trial available for DraftView?

Accepted Answer

DraftView is in early access. There is a free tier for small teams and individual users, with paid plans for larger teams and enterprises. Join the waitlist for more details on pricing.

The DraftView Blog

Why Non-Technical Reviewers Won't Use GitHub (And How to Fix It)

Docs-as-Code Review Workflow: The Complete Guide for 2026

The Hidden Cost of Reviewing Documentation in Google Docs

How to Get SME Sign-Off on Documentation Without Leaving GitHub