Docs/uxw/warning messages new

[Susanne254]

💡 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	42ef816
🔍 Latest deploy log	https://app.netlify.com/projects/industrial-experience/deploys/697343fa8dd6bf000885179d
😎 Deploy Preview	https://deploy-preview-167--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 @Susanne254, 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 significantly enhances the project's UX writing guidelines by adding detailed documentation for several types of user messages and interface elements. The aim is to standardize how information is conveyed to users, ensuring clarity, consistency, and effectiveness across the application. These additions provide clear rules and examples for crafting user-friendly text, ultimately improving the overall user experience.

Highlights

• New UX Writing Guidelines: Introduced comprehensive documentation for various UX writing aspects, including non-critical information messages, progress updates, time-related messages, toast messages, tooltips, and warning messages.
• Structured Guidance: Each new guideline document provides 'Dos and Don'ts' examples, best practice templates, and general rules to ensure consistency and clarity in user-facing text.
• Documentation Structure Update: The main 'writing-style-guide-getting-started.md' file was updated to remove redundant 'Read more' links, streamlining navigation within the documentation.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces new markdown files to document guidelines for non-critical information messages, progress updates, time-related messages, toast messages, tooltips and warning messages. The reviewer pointed out several issues such as a missing value for sidebar_position, an incorrect frontmatter key (Sidebar_lable should be sidebar_label), invalid HTML for line breaks in a table, incorrect apostrophes that should be replaced with the right single quotation mark, and the use of three periods instead of the Unicode ellipsis character.