Skip to main content

Documentation, organized like a product.

A calm map—from first steps to deep reference—without getting lost.

Why it matters: Good documentation respects your time.

Concepts.

Why it works the way it does.

Three-Layer Architecture

API → Domain → Storage. Clean separation, clear responsibilities.

Business Rules & Events

Before/After hooks on every operation. Extensibility without hacks.

Generated vs Custom

What's regenerated, what's preserved. Extension points matter.

Module System

Composable microservices. Cache, Logging, Notification, Security, Work.

Documentation principles.

What We Do

  • Versioned docs with last-updated dates
  • Search that actually works
  • "No mystery behavior" principle

Boundaries

  • No outdated docs without warnings
  • No mystery behavior—if it's not documented, it's a bug

Control

  • Version selector for your deployment
  • Feedback mechanism on every page

Find what you need.

Start with guides or dive into the API reference.