Project Structure

Projects using renderpptx will have the same general layout as renderpdf projects as seen in the example below:

└── project/
    ├── callback/
    ├── error/
    ├── mediaproxy/
    ├── renderpptx/ --> new folder
    ├── restapi/
    └── upload/

In the renderpptx folder, we will include all necessary files as below:

Simple Example:

tenants/
└── <tenant>
    └── projects/
        └── <project>
            └── renderpptx/
                ├── powerpoint/
                │   └── default.pptx
                └── config.ion

The config.ion contains general configuration for the renderer. The configuration supports profiles and inheritance.

The powerpoint directory must at least contain a PowerPoint template.

The default name for PowerPoint template is default.pptx. If the API is called a different documentTemplate parameter say for instance documentTemplate=extra, then a PowerPoint template extra.pptx is expected to exist.

The PowerPoint directory may contain an images subdirectory. This can contain additional file resources needed for rendering. E.g., it can contain 'local' or 'static' images, that are not stored on an external server but next to the template.

Extended Example:

tenants/
└── <tenant>
    └── projects/
        └── <project>
            └── renderpptx/
                ├── powerpoint/
                │   ├── default.pptx 
                │   ├── extra.pptx      // alternative template used with API call 'documentTeamplate=extra'
                │   └── images/
                │       └── mynews.png  // local image - accessible via location 'resources/mynews.png'
                │── config.ion
                └── config-extra.ion    // additional config used with API call 'profile=extra'