PraisonAI PPT Documentation

Create beautiful PowerPoint presentations from Bible verses with integrated PDF conversion

View the Project on GitHub
MervinPraison/PraisonAIPPT

Pipeline architecture

Pipeline architecture

PraisonAI PPT separates orchestration (QA gates, sync, reports) from implementations (PPTX build, MP4 compositor). Deck config is YAML or JSON with the same schema.

Layers

flowchart TB
  subgraph entry [CLI]
    Main["praisonaippt -i deck.yaml"]
    Pipe["praisonaippt pipeline"]
    Val["praisonaippt validate-deck"]
  end
  subgraph load [Load]
    Loader["loader.load_verses_from_file"]
    Validate["schema + yaml_validate"]
  end
  subgraph orch [Orchestration]
    DP["deck_pipeline.run_pipeline"]
  end
  subgraph proto [Protocols]
    PB["pipeline_protocols"]
  end
  subgraph impl [Implementations]
    Core["core.create_presentation"]
    VE["video_exporter.convert_deck_to_video"]
  end
  Main --> Loader
  Pipe --> Loader --> DP
  Val --> Loader --> DP
  DP --> PB
  PB --> Core
  PB --> VE
Module Role
loader.py load_deck_mapping (parse only), load_verses_from_file (templates + validate), write_deck_mapping (JSON or YAML write)
yaml_validate.py validate_pipeline, validate_avatar_calibration, validate_video_export, …
video_protocol.py Overlay precedence; transition parse/resolve/validate/timeline
deck_pipeline.py Gates, PipelineOptions, report.json; optional build_fn / export_fn hooks
pipeline_protocols.py Default adapters to create_presentation and convert_deck_to_video
video_presets.py Shared VIDEO_PRESETS for compositor and post-render QC
core.py PPTX generation only
video_exporter.py Manifest + FFmpeg compositor only

Dependency rule: core and video_exporter do not import deck_pipeline.

Entry paths

Path Builds PPTX Builds MP4 Full gates
praisonaippt -i deck.yaml Yes If --convert-video Preflight only (--validate-deck, --validate-pip, sync, seed timing)
praisonaippt pipeline -i deck.yaml Yes (unless --skip-build) If --convert-video All configured gates + report.json
praisonaippt validate-deck -i deck.yaml No No Same gates as pipeline, validate-only

pipeline: block (YAML or JSON)

See Deck reference. CLI flags override YAML where both are set.

Example (examples/heygen-50590-content.yaml):

pipeline:
  content_master: heygen-50590-content.yaml
  transcript_path: examples/short-script-50590_timestamps.json
  auto_sync: true
  validate_pip: true
  variant_prefix: heygen-50590
  content_approved: true
  rights_acknowledged: true

JSON decks use the same keys (see Commands — JSON decks).

CI report

praisonaippt pipeline writes report.json (default: .praisonaippt/{deck-stem}.pipeline-report.json):

HeyGen variant sync

sync-variants copies slide content from a content master into heygen-50590-*.yaml variant files. Masters may be .yaml or .json; variant outputs remain .yaml by convention.

praisonaippt sync-variants -i examples/heygen-50590-content.yaml
python examples/sync_heygen_variants.py   # same operation