Names of the major/minor areas of the Composer screen - UX

[zxyanliu]

I have a few questions about how to name some of the areas of the Composer screen:

The Home page

How to name these areas of the Home page of the Composer screen?

1. The bar that contains Composer product name and bot project that was opend last. A Title bar?
2. The triple-line icon which selected will collapse or display the Composer Menu.
3. What do we call this section? Toolbar?
4. What do we call this area? A Dashboard?

The Design Flow page

How to name these areas of the Design Flow page of the Composer screen?

1. Should we call this area: the dialog navigation pane of the Design Flow page?
2. Should we call this area: the Toolbar of the Design Flow page?
3. What do we call this area?

The Bot Responses page and the User Input page

How to name these areas of the Bot Responses page and the User Input page of the Composer screen?

1. Should we call this area: the dialog navigation pane of the Bot Responses/ User Input page?
2. Should we call this area: the Language Generation (LG) editor / Language Understanding (LU) editor of the Bot Responses/ User Input page?

The Settings page

How to name these areas of the Settings page?

1. Can we call it the navigation pane of the Settings page?
2. Configuration is confusing here.
3. Settings under the Settings option in Menu is duplicating in names.

The Publish page should be consistent in wording which means all deploy should be replaced by publish. This is a known issue - see issue #1688

Thanks!

Yan

[mareekuh]

Lookign great!!

Home page

1. Titlebar - Ok
2. Menu - Ok
3. Toolbar - ok
   1. Note: how do we call the title above (maybe eventually below) the toolbar?
      4. Dashboard - Hmm … does this have to have a name? For ‘Design’ view this is the authoring canvas, for Responses/User Input this is a list… For the home page it is… the home page?

Flow page
1. Navigation pane - How about Menu pane instead?
2. Toolbar - ok
3. ? - This is the breadcrumb bar.

Bot responses
(How about ‘Prompts and responses’?)
1. Bot Response - Page title
2. Navigation pane - ok
3. Bot responses - How about List view? Which can be turned into ‘edit mode’.

Settings page

1. Navigation pane - ok
   2. Configuration -> should be settings. The menu used to say ‘Configuration’ but the nav didn’t get updated. So good point, this is a ux bug. We can get rid of this altogether as the next item already says ‘Settings’ This one should be selected by default.
2. Settings > Settings - yup, that’s annoying duplication

Publish
Deploy -> publish : Yes please, I’ve already created many bugs for this to be changed throughout the app (nav, title, UX copy, doc, doc titles, doc names, buttons etc.). Hopefully after this update we’re done with them (-;

[zxyanliu]

Hey @mareekuh Thanks for your response. I am curious when will the next UX update be as you mentioned above? We writers might need to get prepared for changes in our docs. Thanks!

[WashingtonKayaker]

My thoughts:

The Home page

1. In Azure this section is referred to as the "Page header" (See Azure portal overview).
2. Not sure the name (of the 3 horizontal bars), I'd go with Menu icon. The descriptive terminology should be something like:
   • The Composer menu is a flyout panel, it's collapsed until you need it. Select the menu icon to expand or collapse the menu.
   • You can collapse the Composer menu to provide more working space.
3. Toolbar
4. Dashboards are "customizable interactive signboards that provide real-time information. Dashboards are associated with a team or a project and display configurable charts and widgets". See About dashboards, charts, reports, & widgets, so I'm not sure that the word dashboard fits. Perhaps just home page, or ???

The Design Flow page

1. Navigation pane. I think it is OK to refer to it as that regardless of which page you are in. the Design Flow can have a Navigation pane as well as the Bot Responses or Settings page etc. You do not need to add the full description when referring to it (i.e. "the dialog navigation pane of the Design Flow page"), just Navigation pane.
2. Toolbar. You do not need to add the full description when referring to it (i.e. "the Toolbar of the Design Flow page"), just Toolbar.
3. Breadcrumb

The Bot Responses page and the User Input page

1. Navigation pane. I think it is OK to refer to it as that regardless of which page you are in. the Bot Responses page can have a Navigation pane as well as the User Input page etc. You do not need to add the full description when referring to it (i.e. "the dialog navigation pane of the Bot Responses/ User Input page"), just Navigation pane.
2. My vote is LG editor / LU editor.

The Settings page

1. Just call it "Navigation pane". Alternatively it can be called "The settings menu", although the naming for this page may need revisited, the main Composer menu is named Settings and the option in the navigation pane (or settings menu) is also Settings, this is confusing.
2. Yes, Configuration is confusing here... Does this "navigation pane" even need a title? what purpose does it serve?
3. "App Settings" or "Application" - for the same reason the filename when developing bots using the SDK is Appsettings.json.

Question regarding use of the term "Publish". Is it more accurate to use the term "Publish" or "Deploy" / "Deployment"? Once that is settled, it needs to be consistent.

The list of items in the "navigation pane" or "settings menu" are all settings:

1. Application settings
2. Deployment settings
3. Onboarding setting

The names given should reflect what settings they are, and the word "settings" can be removed because it is implied by the fact that they are all in the Settings menu. The menu items should be:

1. Application
2. Deployment
3. Onboarding

[zxyanliu]

Thanks! @mareekuh @WashingtonKayaker. Here is my conclusion and votes:

The Home page

1. Title bar - I searched: PVA docs, Window decoration, Title bar
2. The Menu icon
3. Toolbar
4. Home page (if necessary)

The Design Flow page

1. Navigation pane
2. Toolbar
3. Breadcrumb

The Bot Responses page and User Input page

1. Navigation pane
2. LG editor / LU editor

The Settings page

1. Navigation pane
2. Remove Configuration
3. Configure, Publish, and Onboard

[WashingtonKayaker]

Title Bar Vs Page Header

[zxyanliu]

Closing this issue.

[zxyanliu]

The Settings page contains repetitive Settings, and Configuration seems to be unnecessary.