# Kaltura Documentation Platform

> From source code to docs — for people and agents.

---

Services publish what they know. The registry keeps it. The docs site turns it into pages, llms.txt, and Nova agents.

## How It Fits Together

```
PUBLISH                    STORE                       BUILD                 CONSUME
Microservices (OpenAPI) ─┐                                               ┌→ docs.kaltura.com
                         ├→ Platform Content Registry ─→ Documentation ──┼→ llms.txt · .md (AI agents)
Experiences (SDK docs) ──┘          │                    Site            └→ Nova agents
                                    └→ MCP tools                ↑
Hand-written markdown ──────────────────────────────────────────┘
```

## Explore the Platform

### Documentation Site

Minisites, the build pipeline, and Nova agents.

- [How Docs Are Structured](/docs/how-docs-are-structured)
- [Documentation Sources](/docs/documentation-sources)
- [How to Update Docs](/docs/how-to-update-docs)

### Platform Content Registry

One source of truth for specs and SDK docs.

- [Overview](/docs/platform-content-registry/overview)

### Experiences

SDK packages documented from guides and TypeScript source.

- [Overview](/docs/experiences/overview)

### API References

Microservice REST APIs, generated from OpenAPI on every deploy.

- [Overview](/docs/api-references/overview)
- [Onboarding a Microservice](/docs/api-references/onboarding)
- [OpenAPI Spec Quality](/docs/api-references/spec-quality)
- [Staging & Production](/docs/api-references/deployment)
- [Updating the Quality Skills](/docs/api-references/updating-quality-skills)

## Start a Task

- [Update documentation](/docs/how-to-update-docs) — edit or add pages with Claude
- [Onboard a microservice](/docs/api-references/onboarding) — publish its OpenAPI specs
- [Set up an experience](/docs/experiences/overview) — document an SDK package
- [Improve spec quality](/docs/api-references/spec-quality) — score and fix at the source