Skip to content

docs: Polish README with corrections and helpful guides#457

Open
KushguptaPST wants to merge 1 commit intovolcano-sh:masterfrom
KushguptaPST:fix-readme-improvements
Open

docs: Polish README with corrections and helpful guides#457
KushguptaPST wants to merge 1 commit intovolcano-sh:masterfrom
KushguptaPST:fix-readme-improvements

Conversation

@KushguptaPST
Copy link

Hi everyone! 👋

I noticed the README had a few small typos and some outdated info, so I gave it a bit of a polish to help new contributors get started more easily.

Here is a summary of the changes:

  • Fixed typos: Corrected phrases like "How to contributing" to "How to contribute".
  • Updated installation steps: Updated outdated Hugo version references and added Windows (Chocolatey/Scoop) instructions.
  • Added new guides: Added "Project Structure", "Troubleshooting", and "Getting Help" sections to assist new users.

Fixes #439

@volcano-sh-bot volcano-sh-bot added the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jan 30, 2026
@volcano-sh-bot
Copy link
Collaborator

[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 k82cn for approval. For more information see the Kubernetes Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@volcano-sh-bot
Copy link
Collaborator

Welcome @KushguptaPST! It looks like this is your first PR to volcano-sh/website 🎉

@gemini-code-assist
Copy link

Summary of Changes

Hello @KushguptaPST, I'm Gemini Code Assist1! 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 README.md file to provide a more polished, accurate, and comprehensive guide for new contributors. The changes aim to streamline the setup process, clarify project organization, and offer immediate support for common issues, ultimately lowering the barrier to entry for anyone looking to contribute to the project.

Highlights

  • Typo Corrections: Several grammatical errors and typos within the README.md file have been fixed to improve clarity and professionalism.
  • Enhanced Installation Guide: The Hugo installation instructions have been significantly updated, including recommendations for the extended version, a note on version compatibility with netlify.toml, and detailed steps for Windows users via Chocolatey and Scoop.
  • New Informative Sections: New sections have been added to the README.md covering 'Project Structure', 'Troubleshooting' common issues, and 'Getting Help' for new contributors, making the onboarding process smoother.

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

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.

@volcano-sh-bot volcano-sh-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 30, 2026
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

Hi! Thanks for this great contribution. You've done an excellent job polishing the README.md file. The typo fixes, updated installation instructions, and especially the new 'Project Structure', 'Troubleshooting', and 'Getting Help' sections are fantastic additions that will make it much easier for new contributors to get started. The updated instructions are clearer and more maintainable. I have a couple of minor suggestions to further improve the formatting and consistency. Overall, this is a very helpful set of changes!

Comment on lines +40 to +44
* **/content**: Contains the markdown files for the website content.
* **/static**: Contains static assets like images, CSS, and JavaScript.
* **/themes**: Contains the Hugo themes used for the website.
* **/layouts**: Contains custom HTML templates.
* **/config**: Contains Hugo configuration files.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better readability and to follow common Markdown conventions for file paths, consider using backticks to format the directory names as code. This will also make them stand out more clearly as paths. The glob-like **/ prefix seems unnecessary here as these are top-level directories.

Suggested change
* **/content**: Contains the markdown files for the website content.
* **/static**: Contains static assets like images, CSS, and JavaScript.
* **/themes**: Contains the Hugo themes used for the website.
* **/layouts**: Contains custom HTML templates.
* **/config**: Contains Hugo configuration files.
* `content`: Contains the markdown files for the website content.
* `static`: Contains static assets like images, CSS, and JavaScript.
* `themes`: Contains the Hugo themes used for the website.
* `layouts`: Contains custom HTML templates.
* `config`: Contains Hugo configuration files.


> **Note:** The `netlify.toml` file specifies the Hugo version used for production builds. For local development, it is generally safe to use a newer version, but if you encounter issues, try matching the version in `netlify.toml`.

#### Mac OS X

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency and to use the current naming convention, consider changing "Mac OS X" to "macOS".

Suggested change
#### Mac OS X
#### macOS

Correct typos and update outdated Hugo version references.
Add new sections for Windows installation, Troubleshooting, and Getting Help.

Signed-off-by: KushguptaPST <kushg0082@gmail.com>
@KushguptaPST KushguptaPST force-pushed the fix-readme-improvements branch from 96e493c to 3ca7d7e Compare January 30, 2026 15:36
@volcano-sh-bot volcano-sh-bot removed the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jan 30, 2026
@KushguptaPST
Copy link
Author

KushguptaPST commented Jan 30, 2026

Hi @JesseStutler @Arhell @amye please look into my changes .
I have already done many good documentation changes ....please approve my request and assign me this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(docs) : Update README.md with corrections and comprehensive documentation improvements

2 participants