Skip to content

Introduction

DraftStack keeps developer documentation current after code changes land.

Connect a documentation repository, choose one or more monitored source repositories, and let DraftStack inspect merged pull requests. When a change affects readers, DraftStack drafts a focused documentation update for review.

DraftStack does not publish directly. Reviewers approve a suggestion first, then DraftStack opens a draft GitHub pull request in the documentation repository.

Use DraftStack when product behavior changes faster than the docs review cycle. It works best for API routes, CLI commands, configuration fields, setup flows, and user-facing behavior that appears in code diffs.

Use regular human editing for narrative docs, release positioning, and pages that need product judgment beyond the pull request.