plugin-template — the starter
The fork-and-go plugin starter — the SDK tutorial as a runnable repo that consumes only the published @paged-media packages.
In short plugin-template is the shortest path to a working plugin — a
runnable starter that consumes only the published @paged-media packages (no
workspace links). It's the living proof that the Plugin SDK
works from a clean checkout.
What it gives you
- A minimal manifest +
activate()skeleton that loads in the editor. - A dependency setup floating on the published canary packages, with a standing CI lane that proves the clean-checkout build.
Follow Build a plugin to go from this template to a shipped bundle.
Recent activity
- 2026-10-02docs: add docs/ in the structure the paged-media repositories share3ddee4f
- 2026-10-01template: plugin-api / plugin-sdk are peers, as in every first-party bundle86e0294
- 2026-09-10deps: refresh within declared rangesa69405e
- 2026-08-18template: declare the keybindings capability the tutorial uses (10-week canary red)4cd2018
- 2026-06-07deps: float on the canary dist-tag + standing canary CI lane (W3.11 / P31/P33)e3dcd8d
- 2026-06-06Fork-and-go plugin starter — the docs tutorial as a runnable repoddaa41b
paged.publish — IDML and PDF
The format plugins — IDML import and export that round-trips InDesign packages byte for byte where nothing changed, and PDF opened as an editable native document.
Paged vs InDesign, QuarkXPress, Affinity, Scribus & DesignCraft
How Paged compares to the major desktop-publishing tools — an open-source, IDML-compatible, scriptable platform measured against the incumbents on a dated capability matrix.