Create UI-terminology.md

[Susanne254]

First off, thanks for taking the time to contribute! ❤️
We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

💡 What is the current behavior?

No page for UI terminology.

🆕 What is the new behavior?

New page UI terminology in menu functions and UI labels added.

👨‍💻 Help & support

[netlify]

✅ Deploy Preview for industrial-experience ready!

Name	Link
🔨 Latest commit	5986799
🔍 Latest deploy log	https://app.netlify.com/projects/industrial-experience/deploys/69c65b7446a63f00083a05bc
😎 Deploy Preview	https://deploy-preview-208--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, 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 establishing consistent UI terminology across products. The goal is to improve user understanding, reduce ambiguity, and streamline communication by providing clear definitions and usage guidelines for various UI actions, elements, and interactions, adaptable for different input methods and platforms.

Highlights

• New UI Terminology Documentation: A new documentation page, 'UI-terminology.md', has been added to provide comprehensive guidelines for consistent UI language.
• Platform-Specific Interaction Terms: The document includes specific terminology for desktop (mouse), mobile (touchscreen), and keyboard interactions, emphasizing the use of 'select' for multi-platform applications.
• Clarification of Confused Terms: Detailed explanations are provided for commonly confused UI interaction terms, such as 'add vs. create', 'upload vs. import', and 'delete vs. remove', with definitions and examples.
• UI Element and Paired Terminology: Guidelines for consistent UI element naming (e.g., 'checkbox' over 'tick box') and a list of common opposite and paired terms (e.g., 'Activate' / 'Deactivate') are included.

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.

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 adds a new documentation page for UI terminology, which is a valuable addition for ensuring consistency. The content is well-structured and comprehensive. However, there are several violations of the repository's documentation style guide, particularly concerning typography (use of curly quotes and apostrophes). I've also noted a minor grammatical error, an inconsistency in punctuation, and a few placeholder links that need to be addressed. Please see my detailed comments for suggestions on how to align the document with the established guidelines.