Learn more about the
platforms folder, which is represents the voice platform projects, including information and language models.
platforms folder includes all the information you need to deploy the project to the respective developer platforms Amazon Alexa and Google Assistant.
At the beginning of a new project, the folder doesn't exist until you either import an existing Alexa Skill project with
jovo get, or initialize the platforms with
jovo init and then create the files from the Jovo Language Model with
jovo build (see CLI > Workflows for examples).
If you only want to work with a platform specific model, for example, you want to create just an Alexa Skill, you don't necessarily need the
/models folder: The
/platforms folder and the
jovo deploy command are enough. Go to Jovo CLI to learn more about all commands.
alexaSkill folder contains all the information of your Alexa Skill needed to deploy the skill to the Amazon Developer Portal using the
.ask folder contains the
config file, which has the basic deploy settings of your skill. We recommend you to not make any changes to this file.
The Alexa Interaction Model is stored in this folder. It can either be built by the
jovo build command (if you're making use of the Jovo Language Model), updated manually, or updated in the Amazon Developer Portal and then imported with
For more information about Alexa Interaction Models, please see the official reference by Amazon: Custom Interaction Model Reference (Intents, Slots, Sample Utterances).
skill.json contains the publication and configuration information of your Skill. This can be either updated manually or in the Amazon Developer Portal (and then imported with the
jovo get command).
googleAction folder currently contains the
dialogflow (as supported natural language understanding tool) folder with all the files needed to deploy the agent to Dialogflow Console using the
Please note that Jovo currently supports Dialogflow v1, which means that you can't programmatically create or update your agent. However, the
jovo deploy command will create a
zip which you can then import into Dialogflow.
It will be stored inside the
dialogflow folder contains the following folders:
intents are saved in separate files and look like this:
It is important that
"webhookUsed" is set to
true for your Jovo code to be triggered when this intent is called.
The user phrases are added to a different file for each language, e.g.
MyNameIsIntent_usersays_en-us.json, and look like this:
If you have defined input types, you will find the
entities in separate folders as well.
This includes some agent specific information. We recommend to not change this file unless you know what you're doing.
Subscribe to our free newsletter to receive updates and tutorials on Jovo and voice interfaces in general.
Any specific questions? Just drop them below. Alternatively, you can also fill out this feedback form. Thank you!