Quick Start

Getting started with DevDocs.dev.

Introduction

DevDocs.dev is a developer documentation product for teams that need more than static pages. It pairs readable docs with OpenAPI playgrounds, SDK-ready references, CLI-in-the-web, sandbox-in-the-web, and guided walkthroughs that work for both humans and AI systems.

Want the bigger picture?

Read Getting Started for the first-run reader journey and Platform Architecture for the system split.

Terminology

Docs surface: The public site at devdocs.dev, designed for readers, reviewers, developers, AI agents, and stakeholders.

Control plane: The authenticated admin experience at admin.devdocs.ai, used for previews, publishing, and domain management.

Proof loop: The verification path that combines local checks, preview review, and post-merge production confirmation.

Review the product shape

Start on the public docs site

The docs shell should feel like a polished developer reference site, not an application dashboard. That means clear hierarchy, a strong table of contents, predictable navigation, and enough depth for API, SDK, and walkthrough content.

Move into operations only when needed

Readers stay on the docs surface. Operators switch into the control plane only for work that actually requires authentication or operational access.

Verify before promotion

Changes should travel through previews, a review battery, and production checks before they are treated as done.

Use this section for the pages readers need first: quick start, architecture, and authoring guidance.

Use this section for preview review, release proof, roadmap work, and domain promotion flow.

Use this section to show the docs shell carrying richer UI and content patterns without losing readability.

FAQ

Learn More

On this page