Learn how to use a CMS for your Alexa Skills and Google Actions with the Jovo CMS integrations.
The Jovo CMS Interface is an abstraction layer for managing and localizing content for your voice apps. By default, i18next JSON support is enabled, which can be extended with cloud-based CMS integrations like Google Sheets.
Here is a list of all available CMS integrations for Jovo:
| Name | Description |
|---|---|
| Google Sheets | Manage content in a Google Spreadsheet |
| Airtable | Manage content using Airtable |
The Jovo CMS integrations interface offers features that are available acros CMS platforms, like:
For all features of a CMS integration, take a look at the specific docs of the available integrations above.
This feature uses the Jovo i18next integration to creat localized content with specific features for voice and conversational experiences:
- multilingual apps
- randomized output
- platform-specific responses
The content of the CMS interfaces is by default retrieved when the Jovo app is initialized (e.g. when the server starts with jovo run or when the Lambda function does a cold start) and then stored into the app object (learn more about app data here). This is configured with the default configuration caching: true for each CMS integration.
For some use cases (like testing), however, it might make sense to retrieve the CMS with every request. You can enable these instant updates by setting the caching option to false.
Learn how to enable this option in the documentations of the available integrations above.
Take a look at the implementation of the Jovo GoogleSheets CMS to get an understanding of how to build your own CMS integration.