Docs conversational design updates #152
Conversation
❌ Deploy Preview for industrial-experience failed.
|
Summary of ChangesHello @tokyojen, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on enhancing the clarity and consistency of the conversational design documentation. The changes involve refining the recommended tone of voice and specific interaction phrases for chatbots, updating terminology for problematic wording, and making minor textual corrections to improve overall accuracy and guidance. The aim is to provide more precise and effective guidelines for designing chatbot interactions. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces several updates to the conversational design documentation. The changes primarily focus on refining wording, terminology, and section titles for better clarity and consistency. I've identified a couple of minor style guide violations concerning trailing whitespace which should be corrected. Overall, the updates improve the quality of the documentation.
|
|
||
| **5. Decide on your chatbot’s tone of voice:** | ||
| - Is it friendly? Conversational? Formal? Humorous? Direct? Intimate? Respectful? Serious? Casual? | ||
| - Is it conversational? Formal? Professional? Direct? Respectful? Serious? Engaging? |
There was a problem hiding this comment.
This line has trailing whitespace at the end. According to the repository style guide, lines should not end with whitespace characters.
| - Is it conversational? Formal? Professional? Direct? Respectful? Serious? Engaging? | |
| - Is it conversational? Formal? Professional? Direct? Respectful? Serious? Engaging? |
References
- No whitespace at the end of lines. (link)
| </DoAndDont> | ||
|
|
||
| ## Problematic wording to avoid | ||
| ## Cognitive and emotional wording to avoid |
There was a problem hiding this comment.
This line ends with a non-breaking space character (U+00A0), which is considered trailing whitespace. The repository style guide requires that lines do not end with whitespace.
## Cognitive and emotional wording to avoid
References
- No whitespace at the end of lines. (link)
💡 What is the current behavior?
GitHub Issue Number: #
🆕 What is the new behavior?
Changes to the sections based on the new wording section - no FIgma changes yet though so we can wait to publish until FIma is ready or just merge so the wording and paragraphs are updated.
👨💻 Help & support