The missing review layer for GitHub

Overview•4 min read|
|

DraftView is the collaborative layer for all the docs in your Git workflow. Engineers stay in the pull request. Everyone else reviews the rendered page.

Engineers write documentation in Git, but people who validate accuracy (including product managers, support teams, and legal counsel) often struggle to review raw Markdown or Git diffs. DraftView lets non-engineers review the rendered document, while keeping your Git repository as the source of truth.

What DraftView adds to your workflow

  • Invite everyone: Share a pull request or files on a branch. Reviewers join by email and start reading immediately, without needing a GitHub account.
  • Control who does what: Give each person or share link a clear role: view only, comment, or edit.
  • See the page, not the markup: Markdown, MDX, and AsciiDoc render the way readers will see them, with tables, callouts, and Mermaid diagrams intact.
  • Decide together. Keep the record: Comment threads, suggested edits you accept or reject, and a full audit trail of every decision. Insights shows how your reviews are progressing.

The human review layer for AI-generated docs

When AI assistants open documentation pull requests faster than teams can review them, review speed stays human. DraftView prevents rubber-stamping by providing a visual review canvas, verifying whether follow-up revisions fixed commented regions, and recording evidence of human oversight before merge.

DraftView does not replace GitHub. Your repository remains the source of truth, and your team still merges in GitHub.

Start here