OpenPresentation status — September 15, 2026
The public JSON/slide demo and reusable authoring foundation are available. Shared headers/footers are validated on main. Four unfinished shaping prototypes are preserved on remote archive branches and tracked in the roadmap; their original PRs conclude with documentation/evidence changes only.
Read the current handoff, next-agent prompt and developer adoption roadmap. Earlier dated checkpoints are historical evidence, not current release claims.
| Area | Current state |
|---|---|
| Public demo | Home/playground support editable OPF JSON, live preview, preview edits back to JSON, contextual catalog choices and normal code-editor assistance. Appearance is preserved. |
| Published packages | Core0.10.0, renderer0.8.0, editor0.7.0, PPTX0.8.0 and CLI0.8.0 were confirmed in the registry. This final cleanup publishes no additional versions. |
| Developer foundation | Schemas/catalogs, six agent skills, contextual lint/contracts, source-preserving edits/undo, composition/pagination, preview and supported exports exist. Feature and platform limits apply. |
| Shared headers/footers | Core79, renderer20, editor17 and PPTX34 are merged with passing main CI. This increment needs new coordinated versions and consumer adoption. |
| Font shaping/prepared editing | Core83, renderer21, editor21 and PPTX35 retain complete prototypes on archive branches. Final PR diffs contain roadmap/evidence only. Linux native-width failures and an editor packed-test assertion remain recorded, not waived. |
| Native PowerPoint | Acceptance is separately tracked in core issue87. Serialization and self-import do not certify Office. |
| Production checks | Latest retained deployed checks passed 26 main-site, five gallery and ten pptx.dev workflows. See the handoff for commits/evidence. |
The original twenty-PR queue comprises eleven accepted dependency updates, four accepted furniture increments, four roadmap-only conclusions and one closed Node26-types update because the ecosystem targets Node24. Check the linked PR states for final merge/check receipts; merging a roadmap does not release its archived prototype.
Next: release the accepted increment, provide one independently installable developer example with current API/version docs, and adopt shared behavior across the public sites. Broader font/IME/bidi coverage, native Office evidence, layout repair and full visual-editor coverage remain roadmap work. Selectable vector PDF and general SVG/Mermaid follow font reliability.