Orgs, On-Prem, Private Authoring

Quick overview of what and why

- Org = company or BU?
- Private authoring = ?
- Authoring Environment = ?
- Account level = org level?

UI created?

Impact on existing UI?

Questions for me?
- Controls unavailable for role: hide/disable?






Jargon delivers team productivity across the dev & ops lifecycle. Say goodbye to spreadsheets, 

---

Focus on build and logic, not response content and routine content updates

Revert to Rasa underlying file structure as needed - no lock-in

Reduce tool and file switching 
[implied in "IDE"]

Single source of truth - keeps everyone in sync and updated

- Maintain context (highlight how the inspector provides context while staying within the story) - use a basic component

- Understand the story (highlight how the sample dialogue presents a comprehendible view of the story)
[Know how it fits in]

I think the main value of the sample dialogs is when editing smaller components: intents, responses and actions, rather than stories and rules. We could play it up more in that context; it's already fairly prominent in the new hero image (on the CMS side), but maybe it deserves a dedicated place where we talk about it in IDE context.

Jargon catches cross-platform content issues before they become your users' problems.

---

Jargon's intelligent IDE simplifies authoring and connecting the various Rasa artifacts, and keeps content and logic in sync

Jargon lets you collaborate on content and removes the need to re-train models, redeploy the app or touch code for routine response updates.


Jargon shows how each component fits into actual conversations, using story and NLU data.



Import
- new components only
- modal process
- import report
  - new = yes, existing = no
  - new rejected + reason
  - changed? (value?)
- show me (use fresh)


  
Create Release takes the latest committed component in the Studio, validates it for the selected platforms, and creates a content package (using the SDK structure). The content package can then be downloaded as a JSON file to be uploaded to the app (removing Jargon run-time dependency) or deployed to Jargon’s content server.

Please note: responses and other "app content" can be deployed to the content server, while other components (such as intents and stories) require a release package download for retraining etc.


Yesterday: fixes before the big IDE launch



Work w/ Matt on import UI
Deployment messaging and behavior