docs:uxw_new_messages_Overview

[tokyojen]

New UXW page for the new Messages section. Titled "Overview"

💡 What is the current behavior?

GitHub Issue Number: #

🆕 What is the new behavior?

👨‍💻 Help & support

[netlify]

✅ Deploy Preview for industrial-experience ready!

Name	Link
🔨 Latest commit	aa7eb3f
🔍 Latest deploy log	https://app.netlify.com/projects/industrial-experience/deploys/699842f6ffbb5300081a328b
😎 Deploy Preview	https://deploy-preview-163--industrial-experience.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist]

Summary of Changes

Hello @tokyojen, I'm Gemini Code Assist¹! 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 introduces a new documentation page dedicated to UX writing guidelines for messages. The page aims to standardize and improve the quality of user-facing messages by offering clear rules, examples, and best practices for different message types, ensuring a more intuitive and user-friendly interface.

Highlights

• New Documentation Page: A new documentation page, 'Messages overview', has been added under docs/guidelines/language/ to provide comprehensive UX writing guidelines for various message types.
• Message Type Guidance: The new page includes a detailed table outlining different message types (e.g., Error, Warning, Empty-state, Toast, Tooltips) along with their usage and best practice examples.
• UX Writing Dos and Don'ts: Extensive 'Dos and Don'ts' sections are provided with practical examples covering aspects like sentence casing, avoiding overcommunication, specificity, urgent wording, grammar consistency, and appropriate action labels.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[tokyojen]

Needs to be reviewed by UXW team and then merged and ordered with the whole new messages section in the correct order.

[gemini-code-assist]

Code Review

This pull request introduces a new documentation page for UX writing guidelines on messages. The content is comprehensive and well-structured. I've identified several areas for improvement to ensure consistency and adherence to the repository's style guide. My feedback includes corrections for typos, trailing whitespace, inconsistent capitalization, and formatting issues, particularly in the 'Dos and Don'ts' sections. Applying these suggestions will enhance the document's quality and readability.

[kathrinschalber]

Looking forward to seeing this in our docs 😊 main findings:

• Related section contains absolute or missing links
• Structurally, the use of "General rules" without any other "rules" heading
• Placement/connection of guidelines with matching ix-components
• Some minor formatting topics

[tokyojen]

added I hope by Varun

[tokyojen]

done by Varun

[kathrinschalber]

Some comments were resolved even though I couldn't see any changes.

[kathrinschalber]

Not sure why you touched the charts overview page, but you broke a few things 😅

[kathrinschalber]

Cannot see them here? 🤔

[kathrinschalber]

Sorry, I cannot see it changed here

[tokyojen]

CURRENT STATUS: Preview works locally = all changes requested by Kathrin implemented and tested locally. Wont build or preview after push. Also cannot see what was changed in charts overview. Cannot fix the env. errors.