@openpresentation/opf 0.3.0

0.3.0

Added

• Added docs/how-opf-works.md, a conceptual introduction to the format: the document model, the three content shapes, layouts-as-hints, narrative beats, catalog resolution, and the validation philosophy.
• Added docs/design-resolution.md, an explicit design precedence algorithm (slide design → deck design → resolved theme → engine defaults) with worked examples.
• Added a warnings array to ValidationResult. The validator now warns — never errors — on unknown bare catalog ids (narrative, design.theme, design.colorScheme, design.fontScheme, chart type) and on broken catalog cross-links in audience, purpose, and tone records (recommendedNarratives, recommendedTones). Documents that declare matching inline catalogs.<kind>.records[] or a custom catalogs.<kind>.source are exempt. Warnings never affect valid or assertValid.
• Added spec/README.md orienting readers to the spec directory layout, including what the optional spec/openapi.yaml reference contract is for.
• Bundled example decks and catalog cross-links are now checked for unknown catalog ids in the package test suite.
• Added examples/technical/full-feature-tour.opf.json, a single fixture exercising every major schema surface: intent metadata, organizations and speakers, narrative beat overrides, design with slide-level overrides, assets, inline catalog records, all ten content payload kinds, blocks, regions, hidden slides, and extensions.
• Expanded docs/how-opf-works.md with an anatomy diagram, the region-grid diagram, a catalog-resolution flow diagram, and runnable examples for every content shape, plus a complete small deck. Added the precedence-stack and base-plus-overrides diagrams to docs/design-resolution.md and the region-grid cheat sheet to docs/content-payloads.md.
• Presentation-shaped JSON examples embedded in the shipped docs are now validated in the package test suite, so documentation examples cannot drift from the schema.
• Added span-composition diagrams (sidebar + main, headline band + body, and their combination) to the region docs in docs/how-opf-works.md and docs/content-payloads.md.
• Added a "Start in three steps" section to the README and a root llms.txt index so human and agent adopters both get a direct path from problem to first validated deck.
• Shipped every .opf.json deck under examples/ inside the npm package and exposed them via @openpresentation/opf/examples (examples, galleries, exampleCategories, getExample, getGallery, getExamplesByGallery, getExamplesByCategory). Each example deck is validated against the presentation schema at build time.
• Shipped the top-level docs/*.md reference pages inside the npm package and exposed them via @openpresentation/opf/docs (docs, getDoc). Subdirectories like docs/migrations and docs/plans are intentionally excluded.
• Shipped the upstream README.md markdown at the pinned release version via @openpresentation/opf/repo-readme so consumer sites can mirror it without a network fetch.
• Repositioned the repo docs around the OpenPresentation OSS boundary: specs, catalogs, examples, local validation, and planned local render/edit/convert libraries, with hosted service layers left to downstream applications.

@openpresentation/opf v0.2.2

Canonical JavaScript/TypeScript package for Open Presentation Format.

Install:

npm install @openpresentation/opf

Package: https://www.npmjs.com/package/@openpresentation/opf

Includes OPF schemas, catalog presets, generated TypeScript types, raw spec files, and local validation helpers. Does not render PowerPoint, parse .pptx, call PPTX.dev, or use AI.