Callra already had enough moving parts to deserve a cleaner public explanation: a website analytics product, a durable ingest service, an analytics schema, and a self-hosting story that should stay small.
Why ship docs and blog together
Docs answer stable questions. A blog captures motion.
We wanted one place for setup guidance, architecture trade-offs, release notes, and engineering notes without forcing every time-sensitive idea into the documentation hierarchy.
Why use Fumadocs
Fumadocs gives Callra a boring, reliable content path:
- MDX files in-repo
- static route generation for public content
- shared components for docs pages and long-form posts
- one authoring model for reference material and editorial writing
That keeps the product surface simpler. The content lives in separate docs and blog collections, but the pipeline stays consistent.
What comes next
Expect three kinds of content here:
- setup and operations guidance for running Callra
- design notes about durable ingest and the analytics query layer
- shipping updates as the AI and call observability surface becomes more complete