deck-assembler

Automated presentation assembly builds a complete PPTX from JSON contracts like SlideOutline, StyleGuide, and ImageManifest. It removes manual slide-building bottlenecks by validating assets and rendering cohesive decks directly into a ready-to-deliver file.

Generating a PPTX from DeckContext requires outline.json, style-guide.json, image-manifest.json, chart-manifest.json, and speaker-notes.json under ./tmp/deck/. You also need an images/ directory for assets, with optional strategy-map.json and template-profile.json files.

Custom PowerPoint templates and branding can be applied using an optional template-profile.json file. This enables template-based rendering to apply custom layouts and branding rules alongside the standard DeckContext contracts during slide generation.

Node.js supports programmatic PPTX generation by validating referenced images and applying per-slide rendering via an optional StrategyMap. This approach routes assets and charts flexibly, outputting the final deck to ./tmp/deck/output/presentation.pptx.

Building a cohesive slide deck from a structured outline and style guide is best handled by assembling slides from SlideOutline, StyleGuide, ImageManifest, ChartManifest, and SpeakerNotes. This ensures formatting consistency and accurate asset placement without manual intervention.

Automated PPTX assembly fails when images are missing because the process validates referenced assets within the images/ directory. Ensure all ImageManifest entries have corresponding physical files available before running the deck assembler to prevent routing errors.