Guide Map

Use this page to pick the right Drift guide by role and goal.

If You Maintain A TypeScript Package

• Why: prevent stale docs from reaching users.
• Start here: Getting Started
• Then: Coverage and Health

If You Own CI / Release Quality

• Why: enforce docs quality as a merge gate.
• Start here: CI Integration
• Then: Configuration

If You Maintain A Docs Site For An SDK

• Why: catch option tables drifting from the real API (gaps, ghosts, deprecated inversions).
• Start here: CLI Reference — key-coverage mode
• Then: bootstrap the page→type map with drift docs-map stub

If You Build Internal Tooling

• Why: embed Drift analysis into custom workflows.
• Start here: SDK
• Then: CLI Reference

If You Need Pricing / Packaging Context

• Why: align OSS usage with hosted/enterprise roadmap.
• Start here: Pricing & Packaging
• Then: use the waitlist/contact links in the same page to enter the hosted plan pipeline

If You Are Evaluating Product Fit

• Why: decide quickly whether Drift should be a team gate.
• Start here: Getting Started
• Then: Drift Detection