The Paged Platform
What paged is as a whole system — the render engine, the editor and server, the plugins, the SDK and scripting layer, and the live capability state — alongside the IDML format reference.
In short this half of the site documents paged the application — the system that reads, renders, and edits IDML. The other half, the IDML Reference, documents the format. They cross-link: every IDML feature carries a live badge showing how far paged takes it, sourced from the same capability registry you can browse here.
The two pillars
- IDML Reference — the format itself: package anatomy, geometry, layout, text, styles, typography, tables, color, and the rest. A clean-room living reference, with each construct annotated by its support status in paged.
- The Paged Platform (this section) — the software: the engine, the editor,
the backend, the five content plugins, the Plugin SDK, the
paged.*scripting layer, the live capability state, and how it's all tested.
Start here
- Capability state — the live matrix of what works, at which layer, backed by test evidence. This is the system's source of truth for status, surfaced directly from the registry.
The platform documentation is generated from the system itself wherever possible — the capability registry, the engine's scripting catalog, the plugin manifest schema, the server's OpenAPI spec, and the repos' commit history. When the software changes, these pages change on the next build. See how the capability state works.