FIRST VERSION: 20.0
Note that you must have created/edited some content and set it active before doing this interaction. To know more on how to set content live, please check this article.
1) Creating a version
In order to publish any content, we need to first create a Version.
A Version will contain the status of your content ant the moment of the submission, that will then be enabled to be published, previewed or downloaded. To create a version:
- Go to your Portal, in the publishing tab (If you have Edited/Created anything ready to be published, a number will appear as in the screenshot below).
- Click on the green Submit Changes button. A window will pop up. It lets you choose a name for the version and add any eventual notes. From this window, you will see the current status of the content compared to the previous version created, as you can see the window in the image below.
- Choose to Publish the version as Live (this action is explained at chapter 2a of this article) or Submit it for Review (meaning that a new version will be created, but it will not be visible to end users, so you can review it and then set it live later on).
Once you have created one or more versions, you will see them all listed in the Publishing section.
2a) Publishing Content
In order to make your content visible to the end users, click on the three dots on the side of the version you want to show, then select "Publish as live".
You can change the live version by just setting the desired one as live.
2b) Other Publishing Options
If you have a custom publishing process, and you need to download the content you want to publish:
- Click on the three dots on the right of a version and then click on "Download". You will get a launcher.zip file.
- Move the file to a folder managed by your web server (by default, it could be something like <web root>/launcher).
- Unzip the launcher.zip into the folder.
On *NIX operating systems, verify the correct file permissions.
- Try to access to the config.json file inside the launcher. You can do that from a web browser, by typing the file path in the search bar, as in the following example:
If the browser output is something like the image below, the launcher is correctly set up
ATTENTION: while using the custom deployment process, some optional features (of journeys/tips) could be missing if the backend is not accessible (or not configured in snippet), namely:
- sending survey results as emails (if you have added a survey to richtext of bubble)
- tracking journey feedback (if you have configured a journey to ask for feedback)
3) Testing the deployment
If you want to test a version before actually make it visible to your users, you can preview it in your browser. Please, check this article to know more about previewing a version.