Exeevo Omnipresence

You can export e-Detailers to prepare them for subsequent upload to Exeevo Omnipresence.

You can configure the settings for the exported build in the crms.exeevo-omnipresence object of the e-Detailer settings.

Build structure

The exported e-Detailer for Exeevo Omnipresence has the following build structure:

.
├─assets/
|  ├─common/
|  |  ├─blocks-library/
|  |  └─media/
|  ├─node_modules/
|  ├─slides/
|  |  ├─slide1/
|  |  └─slide2/
|  └─themes/
├─common/
├─js/
└─01_chapter1_slide1.html

Path	Description
assets/	Contains the common assets and block assets for each slide.
assets/common/blocks-library/	Contains the public assets for each block.
assets/common/media/	Contains the common media resources used in the slide: fonts, images, PDF files, and videos. Each type of media resource is stored in its own directory.
assets/node_modules/	Contains the following media assets from the node modules for the e-Detailer: fonts, images, PDF files, and videos.
assets/slides/	Contains the media files for each slide. For example, if the e-Detailer has two slides: slide1 and slide2, the directory includes two subdirectories: slide1 and slide2.
assets/slides/slide1/media/	Contains the following media assets for each slide: fonts, images, PDF files, and videos. Each type of media resource is stored in its own directory.
assets/themes/	Contains the media assets from the e-Detailer themes: fonts, images, PDF files, and videos. Assets for each theme are stored in a separate directory.
common/	Contains the common CSS and JavaScript files for the e-Detailer.
js/	Contains the JavaScript files for each slide.
01_chapter1_slide1.html	Includes the HTML for each slide. The file name depends on the order of the slide in the structure.json file of the e-Detailer. For example, the e-Detailer has two slides: slide1 and slide2 that belong to chapter1. As a result, the exported archive includes two HTML files: 01_chapter1_slide1.html and 02_chapter1_slide2.html.