Documentation discovery

Start with the model, then go deeper.

The public site introduces the product. The docs route points people toward the underlying architecture, terminology, and runtime direction so future product surfaces remain consistent.

Architecture

See how Occasion, Event, Actor, Module, Permissions, Communications, and Assets fit together.

Backend contracts

Understand the API, webhook, server, and worker foundations that power future apps and integrations.

Planning model

Review the language and assumptions behind multi-event coordination, guest flows, and vendor operations.

Current docs routing baseline

This route exists now so the landing app has a concrete documentation entry point. A future dedicated docs surface can expand this into richer navigation without changing the planner-facing CTA story.

Back to homepage