Your Heretto Portal Environments
The Heretto Portal includes environments for development and testing to facilitate your Heretto Portal development.
Heretto CCMS provides the tools you need to have a single source of truth from where you can manage configurations and styling of your portal environments. The Heretto team handles hosting and base code updates.
You can configure and customize your portal using your web browser and your portal environments. We recommend having Heretto CCMS open in one window and a portal environment open in another. You can make configuration and styling changes in the CCMS for the respective environments, then see the change immediately reflected in the portal.
- Preview
A non-public environment where you can preview your work-in-progress changes.
- Staging
- A non-public environment where you can push your final changes to test publish and verify them.
- Production
- A public, live live environment where your visitors can access your content.
You can maintain different config.json files for different environments, which are tagged as environment specific in <data>
elements in your sitemap. For more details on adding config.json files to your sitemap, refer to Customize Heretto Portal.
To customize and test your configuration changes, we recommend using multiple configuration files, along with a CSS file and a JavaScript file, if necessary. For example, you can use one for configuration, one for styling, and one for any JS you want to include. All three will be hosted in the Heretto CCMS and referenced in the sitemap using <data>
elements.
We recommend using different config.json
files, one for each portal environment, to manage your custom configurations of your portal environments. You can have preview, staging, and production versions of the configuration files. Each of them controls a different portal environment and works in conjunction with the base configuration file.
Having multiple configuration files enables you to safely test changes in multiple different environments and save those changes separately from one another. For more information on using multiple configuration files, refer to Configuration Layers and Overrides.
<sitemap>
<title>Thunderbird Sitemap</title>
<sitemeta id="config">
<data href="../config-base.json" name="config"/>
<data href="../config-production.json" name="config-production" type="config" rev="production"/>
<data href="../config-staging.json" name="config-staging" type="config" rev="staging"/>
<data href="../config-preview.json" name="config-preview" type="config" rev="preview"/>
<data href="../custom-styling.css" name="stylesheets"/>
<data href="../custom.js" name="scripts"/>
</sitemeta>
<sitesection/>
<mapref href="../../../_thunderbird_quick_start_guide.ditamap"/>
</sitemap>