ƒxyzƒxyz Docs

Docs Map

How the docs are organized now, and where each kind of material lives.

The previous docs experience mixed guides, raw notes, API reference, theory, and internal architecture into one long sidebar. The structure now separates those concerns into five roots.

Start

Landing pages, quickstart, and orientation.

Guides

Product and member workflows.

Build

Integration and development reference.

System

Current implementation, architecture, and network internals.

Research

Synthesis, repo archaeology, and source-of-truth maps.

What Moved Out Of The Main Path

  • Raw product notes and scratch PRDs are no longer part of the primary navigation.
  • Historical work logs remain valuable, but they are treated as archaeology instead of end-user docs.
  • Deep theory and planning material is surfaced through curated overview pages before you drop into long-form source documents.

If you are new

  1. Documentation
  2. Quickstart
  3. User Guides

If you are integrating

  1. API Reference
  2. REST API Reference
  3. Local Development

If you are auditing or planning

  1. Technical Overview
  2. App Surface Map
  3. Architecture / Current State
  4. Research Atlas
  5. Repository Source Map

The TheNetwork section stays in the docs because it contains real conceptual depth, but it now sits under the System root where it belongs instead of competing with quickstart and API entry pages.

Quickstart

Use the platform, integrate with the API, or run the monorepo locally.

On this page

Docs MapWhat Moved Out Of The Main PathRecommended Reading PathsIf you are newIf you are integratingIf you are auditing or planning