How Documentations Are Structured

Minisites

The docs site is split into independent minisites — each one owns a product area, has its own sidebar, and embeds a Nova AI agent.

Live example: Getting Started is one minisite. Content Management is another. Each has its own pages and sidebar.

Minisites are grouped into categories in the top navbar (Getting Started, Conversational Agents, Rich Media CMS APIs, etc.).

Navbar — category dropdown listing minisites

Inside a minisite — sidebar with pages + Nova agent

Where Content Lives

Content comes from two repositories:

Repository	What's in it	Who edits it
docs-kaltura-com	Markdown sources, YAML manifests, site config	Documentation authors
platform-content-registry	OpenAPI specs, TypeDoc artifacts, experience docs	Service teams (auto-generated)

The registry is currently internal — it will become public, giving external developers access to the same structured data.

Build Pipeline

Authors write content and define site structure. An automated build combines both into the final documentation site.

Nova — Documentation Agent

Nova is an AI assistant embedded in every part of the site. The landing agent on the home page helps users find the right minisite. Each minisite has its own contextual Nova agent with knowledge specific to that product area.

See it live: Visit docs.kaltura.com and chat with the landing agent, or browse to any minisite to see its contextual agent.