This section shows workflows and step by step guides that can be used with the Jovo CLI to create and update projects.
The Jovo CLI (see overview of features here) offers a variety of features to help you build a voice app project faster. As it offers support for the full lifecycle of voice app development, the amount of features can be overwhelming at the beginning. This is why we offer this growing list of workflows which you can use to go through your voice app development process.
There are several steps in the process of building a voice application, which you need to do during the development. Let's go through all of them quickly:
2. Initialize Platforms: If you want to deploy to language model to one of the platforms Amazon Alexa or Google Assistant, you first need to initialize the platforms with the
jovo init command. This will create a file called
app.json with the necessary information to create platform specific files. For example,
$ jovo init alexaSkill will add the following to your
3. Build Platform Files: After the initialization, you can use the
jovo build command to create platform specific project files into the
/platforms folder. This will take the files in
/models to create platform information and language models for each platform provided in the
4. Deploy to Platforms: After creating/updating the files, you can upload them to the voice platforms by using the
jovo deploy command. For Amazon Alexa, you need to first install ASK CLI. For Google Assistant, you need to use the newly created file
dialogflow_agent.zip and import it into an agent on Dialogflow.
Done! You should now be able to test your voice application. Just do
$ jovo run to start the local development server.
Chances are you already have an existing Alexa Skill project on the Developer Portal. This workflow shows how to work with platform specific projects.
1. Create a New Project: First, create a new project with the
jovo new command.
2. Get Alexa Skill: You can use the
jovo get command to import an already existing Alexa Skill (functionality is currently limited to Alexa). This will add all the necessary files into the
Usually, the Jovo Language Model is used as an abstraction layer for cross-platform language models. You now have 2 options:
/platformsfolder, update the files there, and use the
jovo deploycommand to update the Alexa Skill
3. Build Jovo Language Model: Converting an Alexa Interaction Model into a Jovo Language Model by hand can be quite a task for complex models. This is why Jovo offers a reverse version of the
jovo build command, which acts as a converter that uses the files in the
/platforms folder to create/update the files in the
/models folder. Just use
$ jovo build -p alexaSkill --reverse.
Any specific questions? Just drop them below. Alternatively, you can also fill out this feedback form. Thank you!