#app div.v-application--wrap header.elevation-0.v-sheet.theme--light.v-toolbar.v-app-bar.v-app-bar--fixed.primary div.v-toolbar__content

#app div.v-application--wrap main.v-main div.v-main__wrap div div.d-flex.justify-space-between div.container div div.d-flex.flex-wrap div.pa-3 div div.v-card.v-card--flat.v-card--link.v-sheet.theme--light.jargon-project-card div.d-flex.justify-space-between span.jargon-project-card-title.ml-4.mt-3

Modelling dialogue is not an easy task due to the natural complexity of human language. This calls for the mindful design of conversational data to optimize what patterns your assistant learns.



PRODUCT ISSUES
Duplicate Project (introduction without rename created issues)
Validation for IDE (big UX impact; not involved)
Rasa components in new locale (huge UX impact; not involved)
Alexa Directive rename/delete ("must have"; why investing in voice?)


Dealing with warnings


No clear delineation between IDE and CMS.
Called out actual features/benefits.
Dimmed the actual content.