DevDocs Portal

Quick Start

Getting started with DevDocs Portal.

Introduction

DevDocs Portal pairs a public documentation surface with an operator control plane. The public site should feel calm, structured, and easy to scan, while the control plane handles publishing, previews, and domains.

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, 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 reference site, not an application dashboard. That means clear hierarchy, a strong table of contents, and predictable navigation.

Move into operations only when needed

Readers stay on the docs surface. Operators switch into the admin portal only for work that actually requires authentication or control-plane 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, backlog 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