This repository was archived by the owner on Jul 9, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 374
doc: guidelines/help-contents #4354
Merged
Merged
Changes from 8 commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
235ffd0
draft help content guidelines
zxyanliu 5507c28
updates
zxyanliu a42a6fb
Update Composer-help-contents.md
zxyanliu a828e26
Update Composer-help-contents.md
zxyanliu c0b8b06
Add files via upload
zxyanliu c59cb99
Delete error-message.png
zxyanliu b365695
Update Composer-help-contents.md
zxyanliu 41c5f0d
Merge branch 'main' into zxyanliu/guidelines
zxyanliu 8d28ce7
Merge branch 'main' into zxyanliu/guidelines
zxyanliu bb2cb63
addressing feedbacks
zxyanliu 7e724d6
Update Composer-help-contents.md
zxyanliu 680d7ef
Update Composer-help-contents.md
zxyanliu f18d4e4
Merge branch 'main' into zxyanliu/guidelines
zxyanliu c1c3b2e
Merge branch 'main' into zxyanliu/guidelines
zxyanliu 38fdd89
Merge branch 'main' into zxyanliu/guidelines
zxyanliu adf33a7
Merge branch 'main' into zxyanliu/guidelines
zxyanliu 41181f6
Merge branch 'main' into zxyanliu/guidelines
cwhitten d448f29
Merge branch 'main' into zxyanliu/guidelines
zxyanliu 9a3d980
Merge branch 'main' into zxyanliu/guidelines
zxyanliu 8a08c0d
Merge branch 'main' into zxyanliu/guidelines
zxyanliu 9efe7ca
Merge branch 'main' into zxyanliu/guidelines
zxyanliu dc93824
Merge branch 'main' into zxyanliu/guidelines
zxyanliu d307109
Merge branch 'main' into zxyanliu/guidelines
cwhitten File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,137 @@ | ||
| # Bot Framework Composer Help Content Guidelines | ||
|
|
||
| Help contents refer to any texts that appear throughout Composer user interface (UI) that will help users to use the tool. Clear, concise, and comprehensible help contents will improve users' overall learning experience and achieve what they set out to build. | ||
|
|
||
| In this article, we drafted some guidelines on how to write the help contents in Composer UI, including button names, menu names, instructional copy, tooltips, error messages, watermark texts, and help links pointing to [Composer official documentation](https://docs.microsoft.com/composer/). These guidelines are based on [Microsoft guidelines on linking to articles from the user interface](https://review.docs.microsoft.com/help/contribute/contribute-link-to-articles-from-the-user-interface?branch=master), and general observation of [Azure Bot Service](https://azure.microsoft.com/services/bot-service/) and [Power Virtual Agent](https://powervirtualagents.microsoft.com/) User Interfaces. | ||
|
|
||
| This document includes: | ||
|
|
||
| - [Terminology](#terminology) | ||
| - [Guidelines](#guidelines) | ||
| - [General guidelines](#general-guidelines) | ||
| - [Button names](#button-names) | ||
| - [Menu names](#menu-names) | ||
| - [Instructional copy](#instructional-copy) | ||
| - [Tooltips](#tooltips) | ||
| - [Error messages](#error-messages) | ||
| - [Watermark texts](#watermark-texts) | ||
| - [Help links](#help-links) | ||
| - [Resources](#resources) | ||
|
|
||
| # Terminology | ||
|
|
||
| * **Instructional copy**: instructional texts that provide users with information about what to do. | ||
| * **Tooltip**: texts displayed in an informational text box when hovering over an item. | ||
| * **Watermark text**: text that lives inside an edit box or entry field. | ||
| * **Help link**: context-sensitive help (CSH) link added to the user interface to help users with a concept or procedure while using a product. | ||
|
|
||
| # Guidelines | ||
|
|
||
| ## General guidelines | ||
|
|
||
| The general guidelines listed in this section apply to all types of help contents as documented in this doc. | ||
|
|
||
| 1. Be concise. | ||
| 2. Be syntactically accurate. | ||
| 3. Be contextually meaningful. | ||
| 4. Be consistent in language and style within the product and across the product portfolio (related products). | ||
| 5. Use sentence case unless texts contain proper names. | ||
|
|
||
| ## Button names | ||
|
|
||
| 1. Keep names short and limit to **3** words maximum. | ||
| 2. Where possible, reiterate the action to be performed upon click. | ||
| 3. Keep names common, clear, and concise. | ||
| 4. Should only contain letters. | ||
| 5. Don’t use acronyms. | ||
|
|
||
| * **Example**: | ||
|
|
||
|  | ||
|
|
||
| ## Menu names | ||
|
|
||
| 1. Keep names short and limit to **2** words maximum. | ||
| 2. Keep names common, clear, and concise. | ||
| 3. Should only contain letters. | ||
| 4. Don’t use acronyms. | ||
|
|
||
| * **Example**: | ||
|
|
||
|  | ||
|
|
||
| ## Instructional copy | ||
|
|
||
| 1. Limit to **1** phrase or **2** sentences in English. | ||
| 2. When necessary, include a help link pointing to a specific doc. | ||
| 3. Instructional text can be accompanied by illustrations or diagrams, below or next to the copy. | ||
| 4. Meet accessibility guidelines (including how they are invoked and presented). | ||
| 5. Meet Microsoft Fluent design guidelines. | ||
| 6. Don’t use acronyms. | ||
| 7. Don’t use questions. | ||
| 8. Don't repeat the label or name of the element. | ||
|
|
||
| * **Example**: | ||
|
|
||
|  | ||
|
|
||
| ## Tooltips | ||
|
|
||
| 1. Limit to 1 phrase or 2 sentences in English. | ||
| 2. Can include visuals or diagrams. | ||
| 3. Meets accessibility guidelines (including how they are invoked and presented). | ||
| 4. Meet Microsoft Fluent design guidelines. | ||
| 5. Meet accessibility guidelines (both mouse and keyboard hover). | ||
| 6. Do not replace, nor should be used as instructional copy. | ||
mewa1024 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| 7. Do not repeat the label or name of the element. | ||
| 8. Do not include a help link pointing to a specific doc. | ||
|
|
||
| * **Example**: | ||
|
|
||
|  | ||
|
|
||
| ## Error messages | ||
|
|
||
| 1. Say what happened and why. | ||
| 2. Include enough information to help users get out of the erroneous situation. | ||
| 3. Limit to **2 –3** sentences in English. | ||
| 4. Choose the tone that best fits the audience and context (Read the message aloud may help). | ||
| 5. Human-readable (use simple and plain language without referring to implementation details). | ||
| 6. Don’t blame the user and be humble. | ||
| 7. Avoid uppercase text. | ||
|
|
||
| * **Example**: | ||
|
|
||
|  | ||
|
|
||
| ## Watermark texts | ||
|
|
||
| 1. Limit to a single word, a phrase, or a short sentence. | ||
| 2. Can show an example of what information is expected to be filled out in this box. | ||
|
|
||
| * **Example**: | ||
|
|
||
|  | ||
|
|
||
| ## Help links | ||
|
|
||
| 1. Help links should be contextual to the user experience. | ||
| 2. Provide a "Learn more" link or "Documentation" link as in Azure. | ||
| 3. Choose the best article as your help source. | ||
| 4. Link to the specific section of an article if necessary. | ||
| 5. A "learn more" link is usually placed at the end of a string or a UI card or as curated collection of documentation links on a blade. | ||
| 6. Determine the best link text to use, considering accessibility requirements | ||
| 7. May consider creating a [fwlink](https://review.docs.microsoft.com/help/contribute/contribute-link-to-articles-from-the-user-interface?branch=master#create-an-fwlink) and reference it in code. | ||
|
|
||
| * **Examples**: | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
| # Resources | ||
|
|
||
| * [Microsoft contributor’s guide - Links to articles from the user interface](https://review.docs.microsoft.com/help/contribute/contribute-link-to-articles-from-the-user-interface?branch=master) | ||
| * [Writing is designing](https://www.google.com/books/edition/Writing_Is_Designing/y_HJDwAAQBAJ?hl=en&gbpv=1&printsec=frontcover) | ||
| * [What does a UX writer actually do?](https://careerfoundry.com/en/blog/ux-design/ux-writing-what-does-a-ux-writer-actually-do/) | ||
| * [Error Message Guidelines](https://uxplanet.org/error-message-guidelines-6ce257d3d0bd) | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.