Jargon Tutorials

Step-by-Step Instructions on How to Use Jargon

Need Additional Support?

We're here for you and happy to answer questions. Don't hesitate to reach out!

Contact Support

Publishing Content Changes Without Retraining, Redeploying, or Resubmitting Your App

Routine content changes in Jargon can be published to your application in a matter of seconds. There is no requirement to retrain your model or redeploy your application for every content change, which can significantly speed up content editing times. Here are the steps to make and publish a content change in Jargon.

How to edit a response and publish changes in Jargon:

1. Within a project, click on the Studio at the top. This is the main editing environment for making content changes. You will see a search bar on the left to find responses. You can search by name or the content within responses.

2. Click on the name of the response you would like to edit. This will bring up a menu of the components within the response. For example, a response might contain multiple variants and each variant might include several underlying components (text, speech, buttons, images, etc.). Click on one of the components to make a change.

3. Whenever changes are made, there will be a status update at the top notifying you of uncommitted changes. If there are changes made by another team member, it will prompt you to “get latest” to sync with your team members’ changes. To reduce merge conflicts, you must “get latest” and your changes must be committed before deploying a release. You can always undo recent edits by navigating to “More Actions” and clicking the “Undo my changes” button below your profile icon at the top right or by right clicking a folder or response name.

4. When you have committed your changes and are ready to publish to your application, you can create a release by navigating to Releases and click on “Create New Release.” Jargon will run additional content validation checks to ensure there are no errors that will break the logic of the application before releasing. If there are errors, Jargon will identify where to fix them within the studio.

5. When creating a release, you may choose which platforms and locales the release is for and add tags to identify the intended environment, such as staging or production.

6. When ready, hit deploy next to the successful release to make the content available to your application. You can also download the content as a set of JSON files to be manually uploaded to your application, if you prefer to manage content offline.

7. Each release will include release details, which include project ID, content interface ID, and release ID. You can access these by clicking on the “</>” button on the right of a release.

8. Once changes have been committed, you can see a history of these changes within a specific response component under the “history” tab below the text editor. You can click the button to the right to compare the changes that have been made.


Need additional support?

support@jargon.com