Skip to content

User Guide

This section explains how to use Atlas once you already understand the basics and can complete the first-run flow.

The user guide is organized by practical work:

  • prepare configuration and understand outputs
  • validate, publish, and move datasets and catalogs
  • build diffs, query results, and OpenAPI artifacts
  • operate the everyday product surface without drifting into maintainer internals
flowchart TD
    A[Configured Atlas] --> B[Catalog workflows]
    A --> C[Dataset workflows]
    A --> D[Ingest workflows]
    A --> E[Query workflows]
    A --> F[Server workflows]
    A --> G[OpenAPI and API usage]
    A --> H[Policy workflows]

This workflow map shows the practical jobs Atlas users return to most often. The user guide is organized around those jobs so readers can start from the action they need instead of from internal implementation structure.

flowchart LR
    UserGuide[User guide] --> Product[Everyday product use]
    Product --> Reference[Reference lookup]
    Product --> Operations[Operations for production]
    Product --> Architecture[Architecture for deeper understanding]

This second diagram clarifies the section boundary. The user guide should help you use Atlas well, but it should not try to replace the operator runbooks, reference indexes, or maintainer architecture pages.

Pages in This Section

What This Section Is Not

This section is not:

  • the deep system explanation of why the code is shaped a certain way
  • the production operator runbook
  • the complete reference listing of every config key or endpoint

For those, move to:

When to Use This Section

  • you can already run Atlas locally
  • you need to repeat a workflow such as ingest, publish, query, or server startup
  • you want procedure and examples, not just a flat command listing

Purpose

This page explains the Atlas material for user guide and points readers to the canonical checked-in workflow or boundary for this topic.

Stability

This page is part of the canonical Atlas docs spine. Keep it aligned with the current repository behavior and adjacent contract pages.