✨ feat: Migrating from hugo to docusasurus

[katara-Jayprakash]

• What this PR does / why we need it:
  In this issue, i am trying to migrating to docusaurus from hugo version, there are lots of stuff's remaining in this pr, but thought should push it, other can also work on it,
• Which issue(s) this PR fixes:
  feat: Migrating hugo to docusaurus #455

[volcano-sh-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 william-wang 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:

• 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 @katara-Jayprakash, 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 represents a comprehensive architectural shift for the project's website, transitioning from Hugo to Docusaurus. This migration aims to leverage Docusaurus's capabilities for documentation and blog management, streamlining the content generation and presentation process. The changes involve a complete removal of the old Hugo-based site structure, configuration, and content, paving the way for a new Docusaurus-powered experience.

Highlights

• Website Migration: The entire website is being migrated from Hugo to Docusaurus, signifying a fundamental change in the static site generation framework.
• Configuration Overhaul: All Hugo-specific configuration files, including config.toml, languages.toml, menus.toml, and params.toml, have been removed to accommodate the new Docusaurus structure.
• Content Restructuring: Existing custom CSS (custom.css), JavaScript (custom.js), and all Markdown content for blog posts and documentation have been removed, indicating a complete rebuild of the site's content and styling within the Docusaurus framework.
• Git Ignore Updates: The .gitignore file has been updated to reflect Docusaurus-specific build artifacts and dependencies, replacing previous Hugo-related entries.

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

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/fossa.yml

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 marks a significant migration of the project's website from Hugo to Docusaurus. The changes involve removing all Hugo-related files and configurations and introducing a new Docusaurus-based structure. My review focuses on the new Docusaurus setup. While the overall structure is sound, I've identified a few critical configuration issues that need to be addressed. These include an incompatible React version in package.json and a missing search plugin configuration in docusaurus.config.js. I've also provided feedback on improving the .gitignore file for better dependency management and some minor suggestions for the navbar and footer to enhance user experience and accessibility. Addressing these points will help ensure a stable and robust launch of the new Docusaurus site.

[gemini-code-assist]

It's a common best practice to commit package lock files (package-lock.json for npm or yarn.lock for yarn) to source control. This ensures that all developers and CI/CD environments use the exact same dependency versions, leading to reproducible builds. Ignoring package-lock.json can lead to inconsistencies and "works on my machine" issues. Please consider removing this line and committing the appropriate lock file for your project's package manager.

[katara-Jayprakash]

/cc @hajnalmt @JesseStutler have a look at it, sir https://volcano-docusaurus.netlify.app/

[labdhiongithub7]

Hi @katara-Jayprakash , I'm also working on migrating the website from hugo to docusasurus locally. Happy to collaborate and sync up so we don’t duplicate work.

[katara-Jayprakash]

Hi @katara-Jayprakash , I'm also working on migrating the website from hugo to docusasurus locally. Happy to collaborate and sync up so we don’t duplicate work.

for sure! i can help you in locally setting up the branch,it would be great if you can work on docs sections.

[labdhiongithub7]

Hi @katara-Jayprakash , I'm also working on migrating the website from hugo to docusasurus locally. Happy to collaborate and sync up so we don’t duplicate work.

for sure! i can help you in locally setting up the branch,it would be great if you can work on docs sections.

Sounds good, thanks! I’ll start working on the docs section

[Tusharjamdade]

Hi @katara-Jayprakash and @labdhiongithub7,

I think this is the project proposed for the LFX mentorship. As discussed in the Slack thread by @JesseStutler, we should not start this yet and instead wait for the official selection announcement. Starting now might create an unnecessary burden for the maintainers.

[katara-Jayprakash]

Hi @katara-Jayprakash and @labdhiongithub7,

I think this is the project proposed for the LFX mentorship. As discussed in the Slack thread by @JesseStutler, we should not start this yet and instead wait for the official selection announcement. Starting now might create an unnecessary burden for the maintainers.

We’re just experimenting with this PR for now. We don't plan on tagging the maintainers for a formal review or anything yet; we’re just testing things out

[codeEvolveZenith345]

Hi @katara-Jayprakash and @labdhiongithub7,
I think this is the project proposed for the LFX mentorship. As discussed in the Slack thread by @JesseStutler, we should not start this yet and instead wait for the official selection announcement. Starting now might create an unnecessary burden for the maintainers.

We’re just experimenting with this PR for now. We don't plan on tagging the maintainers for a formal review or anything yet; we’re just testing things out

@katara-Jayprakash Do you not think that it is an overkill to blow the CI usage just for experimenting? I personally think that @Tusharjamdade Is right to question the intent of a PR in the repo,

The migration has a lot of decisions only mentor/maintainer is supposed to take and then instruct, I too believe it is meaningless to open an Unnecessary PR that blows CI, If I am not wrong volcano too pays for CI checks, not sure if mentors would agree to this unoptimal approach.

No offence on intent, we all want to create a good impact, but PR and repo centric work can simply be isolated by creating a fork and giving collaborator access to @labdhiongithub7.

Rest is one's personal choice. Apologies for intervention.