[WIP] cloud: add docs for the My TiDB Page

[qiancai]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tangenta for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[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 new documentation for the 'My TiDB Page' in TiDB Cloud, aiming to centralize information on resource and project management. It ensures that users can easily find and understand how to navigate and utilize this core feature. The changes also include necessary updates to the glossary to define related terminology, providing a more consistent and clear documentation experience.

Highlights

• New Documentation Page: A new documentation page, 'Use the My TiDB Page', has been added to provide comprehensive guidance on managing TiDB resources and projects within the TiDB Cloud console.
• Table of Contents Integration: The newly created 'Use the My TiDB Page' documentation has been integrated into the Table of Contents for Essential, Premium, Starter, and general TiDB Cloud documentation.
• Glossary Expansion: The TiDB Cloud glossary has been updated with new definitions for 'Cluster', 'Instance', 'Project', and 'Resource' to support the new documentation and clarify key concepts.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• TOC-tidb-cloud-essential.md
  • Added a link to the new 'Use the My TiDB Page' documentation.
• TOC-tidb-cloud-premium.md
  • Added a link to the new 'Use the My TiDB Page' documentation.
• TOC-tidb-cloud-starter.md
  • Added a link to the new 'Use the My TiDB Page' documentation.
• TOC-tidb-cloud.md
  • Added a link to the new 'Use the My TiDB Page' documentation.
• tidb-cloud/my-tidb.md
  • Created a new documentation file detailing the functionality and usage of the 'My TiDB Page' for managing resources and projects.
• tidb-cloud/tidb-cloud-glossary.md
  • Added a definition for 'Cluster'.
  • Added a definition for 'Instance'.
  • Updated the definition for 'Project' to include details on project types and their usage.
  • Added a definition for 'Resource'.

Activity

• The pull request was opened by qiancai.
• No human activity (comments, reviews) has been recorded yet.

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 adds documentation for the new 'My TiDB' page, including a new documentation file and updates to the glossary. The changes are a good start. I've provided several suggestions to improve consistency, grammar, and adherence to the documentation style guide, focusing on heading structure, use of terminology, and writing style. All suggestions are minor and aim to enhance the clarity and professionalism of the documentation.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[ti-chi-bot]

@qiancai: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-verify	1f9f85f	link	true	/test pull-verify

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.