refactor: rename 'vibing code' to 'vibe coding' for consistency

[1pitaph]

• Update subtitle in Home.tsx (zh/en)
• Update description in docs/index.mdx and docs/zh/index.mdx
• Update README.md and README_EN.md tagline

[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 focuses on a minor but important refactoring of terminology across the project's public-facing content. The primary goal is to standardize the phrase 'vibing code' to 'vibe coding' to improve clarity and consistency in branding and user communication. This change impacts documentation, README files, and the main application's home page, ensuring a unified message for users regardless of their language preference.

Highlights

• Terminology Consistency: The phrase 'vibing code' has been consistently renamed to 'vibe coding' across various user-facing texts to ensure uniform terminology.
• Documentation Updates: The project description in both English and Chinese documentation files (docs/index.mdx and docs/zh/index.mdx) has been updated to reflect the new terminology.
• Readme Tagline Refinement: The taglines in both the main README.md and its English version, README_EN.md, have been adjusted for the updated phrasing.
• Frontend UI Text Alignment: The subtitle displayed on the Home page (frontend/src/pages/Home.tsx) has been updated for both Chinese and English locales to match the new 'vibe coding' terminology.

Changelog

• README.md
  • Updated the tagline from 'vibing code' to 'vibe coding'.
• README_EN.md
  • Updated the English tagline from 'vibing code' to 'vibe coding'.
• docs/index.mdx
  • Modified the description to use 'vibe coding' instead of 'vibing code'.
• docs/zh/index.mdx
  • Modified the Chinese description to use 'vibe coding' instead of 'vibing code'.
• frontend/src/pages/Home.tsx
  • Updated the Chinese subtitle to 'Vibe your PPT like vibe coding'.
  • Updated the English subtitle to 'Vibe your PPT like vibe coding'.

Activity

• No specific activity (comments, reviews, approvals) has been recorded for this pull request 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

The pull request successfully renames "vibing code" to "vibe coding" across all specified files (README.md, README_EN.md, docs/index.mdx, docs/zh/index.mdx, and frontend/src/pages/Home.tsx). This change ensures consistency in terminology throughout the project's documentation and user interface strings. The changes are straightforward and correctly applied, aligning with the stated objective of the pull request.

[Anionex]

Thank you for your suggestion, this change has been reflected in the latest English slogan🚀👍