Fix: Combine three-level dropdown with stutter bug fixes

Signed-off-by: Lakshya Saxena <suntiwari3495@gmail.com>

Author: lakxy

README.md

@@ -1,7 +1,7 @@
 [![Netlify Status](https://api.netlify.com/api/v1/badges/8cf65901-dae4-4826-b32b-17feeebddc86/deploy-status)](https://app.netlify.com/sites/kind-montalcini-bed86a/deploys)
 
+# Creating and updating the docs
 
-# Creating and updating the docs 
 Welcome to the GitHub repository for Volcano's public website. The docs are
 hosted at https://volcano.sh.
 
@@ -11,7 +11,7 @@ is an open-source static site generator that provides us with templates, content
 organisation in a standard directory structure, and a website generation engine.
 You write the pages in Markdown, and Hugo wraps them up into a website.
 
-* Please see [How to contributing](https://github.com/volcano-sh/volcano/blob/master/contribute.md) for instructions on how to contribute, if you are not familiar with the
+* Please see [How to contribute](https://github.com/volcano-sh/volcano/blob/master/contribute.md) for instructions on how to contribute, if you are not familiar with the
   GitHub workflow
 
 ## Quickstart
@@ -21,19 +21,19 @@ GitHub workflow and you're happy to use the automated preview of your doc
 updates:
 
 1. Fork the repo on GitHub.
-1. Make your changes and send a pull request (PR).
-1. If you're not yet ready for a review, add a comment to the PR saying it's a
-  work in progress or add `[WIP]` in your PRs title. You can also add `/hold` in a comment to mark the PR as not
-  ready for merge. (**Don't** add the Hugo declarative "draft = true" to the
-  page front matter, because that will prevent the auto-deployment of the
-  content preview described in the next point.)
-1. Wait for the automated PR workflow to do some checks. When it's ready,
-  you should see a comment like this: **deploy/netlify — Deploy preview ready!**
-1. Click **Details** to the right of "Deploy preview ready" to see a preview
-  of your updates.
-1. Continue updating your doc until you're happy with it.
-1. When you're ready for a review, add a comment to the PR and assign a
-  reviewer/approver. 
+2. Make your changes and send a pull request (PR).
+3. If you're not yet ready for a review, add a comment to the PR saying it's a
+   work in progress or add `[WIP]` in your PRs title. You can also add `/hold` in a comment to mark the PR as not
+   ready for merge. (**Don't** add the Hugo declarative "draft = true" to the
+   page front matter, because that will prevent the auto-deployment of the
+   content preview described in the next point.)
+4. Wait for the automated PR workflow to do some checks. When it's ready,
+   you should see a comment like this: **deploy/netlify — Deploy preview ready!**
+5. Click **Details** to the right of "Deploy preview ready" to see a preview
+   of your updates.
+6. Continue updating your doc until you're happy with it.
+7. When you're ready for a review, add a comment to the PR and assign a
+   reviewer/approver.
 
 ## Previewing your changes on a local website server
 
@@ -46,7 +46,7 @@ See the [Hugo installation guide][hugo-install]. Here are some examples:
 
 #### Mac OS X:
 
-```
+```bash
 brew install hugo
 ```
 
@@ -55,17 +55,17 @@ brew install hugo
 1. Download the Debian package from the [Hugo website][hugo-install].
    Make sure to install the Hugo version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L6) file.
    For example, [hugo_0.57.2_Linux-64bit.deb][hugo_0.57.2_Linux-64bit.deb].
-1. Install the package using `dpkg`:
+2. Install the package using `dpkg`:
 
-    ```
-    sudo dpkg -i hugo_0.57.2_Linux-64bit.deb
-    ```
+   ```bash
+   sudo dpkg -i hugo_0.57.2_Linux-64bit.deb
+   ```
 
-1. Verify your installation:
+3. Verify your installation:
 
-    ```
-    hugo version
-    ```
+   ```bash
+   hugo version
+   ```
 
 ### Run a local website server
 
@@ -74,33 +74,34 @@ local machine, then use your local repo as input to your Hugo web server:
 
 1. Ensure you are in your target branch:
 
-    ```
-    git branch
-    ```
+   ```bash
+   git branch
+   ```
 
-1. Start your website server. Make sure you run this command from the
+2. Start your website server. Make sure you run this command from the
    `/website/` directory, so that Hugo can find the config files it needs:
 
-    ```
-    hugo server -D
-    ```
+   ```bash
+   hugo server -D
+   ```
 
-1. Your website is at [http://localhost:1313/](http://localhost:1313/).
+3. Your website is at [http://localhost:1313/](http://localhost:1313/).
 
-1. Continue with the usual GitHub workflow to edit files, commit them, push the
-  changes up to your fork, and create a pull request. (See the GitHub workflow)
+4. Continue with the usual GitHub workflow to edit files, commit them, push the
+   changes up to your fork, and create a pull request. See [GitHub's documentation on creating pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) for more details.
 
-1. While making the changes, you can preview them on your local version of the
-  website at [http://localhost:1313/](http://localhost:1313/). Note that if you
-  have more than one local git branch, when you switch between git branches the
-  local website reflects the files in the current branch.
+5. While making the changes, you can preview them on your local version of the
+   website at [http://localhost:1313/](http://localhost:1313/). Note that if you
+   have more than one local git branch, when you switch between git branches the
+   local website reflects the files in the current branch.
 
 Useful Hugo docs:
+
 - [Hugo installation guide](https://gohugo.io/getting-started/installing/)
 - [Hugo basic usage](https://gohugo.io/getting-started/usage/)
 - [Hugo site directory structure](https://gohugo.io/getting-started/directory-structure/)
 - [hugo server reference](https://gohugo.io/commands/hugo_server/)
 - [hugo new reference](https://gohugo.io/commands/hugo_new/)
 
 [hugo-install]: https://gohugo.io/getting-started/installing/
-[hugo_0.57.2_Linux-64bit.deb]: https://github.com/gohugoio/hugo/releases/download/v0.57.2/hugo_0.57.2_Linux-64bit.deb
+[hugo_0.57.2_Linux-64bit.deb]: https://github.com/gohugoio/hugo/releases/download/v0.57.2/hugo_0.57.2_Linux-64bit.deb

config/_default/menus.toml

@@ -73,26 +73,33 @@
   weight = 4
   identifier = "features"
 
+[[docs]]
+name = "User Guide"
+weight = 5
+identifier = "user-guide"
+url = "/en/docs/user-guide/"
+
 [[docs]]
   name = "Ecosystem"
-  weight = 5
+  weight = 6
   identifier = "ecosystem"
 
 [[docs]]
   name = "Scheduler"
-  weight = 6
+  weight = 7
   identifier = "scheduler"
 
 [[docs]]
   name = "CLI"
-  weight = 7
+  weight = 8
   identifier = "cli"
 
 [[docs]]
   name = "Contribution"
-  weight = 8
+  weight = 9
   identifier = "contribution"
 
+
 # Documentation version v1.12.0
 
 [[v1-12-0]]

content/en/docs/user_guide.md

@@ -0,0 +1,35 @@
++++
+title = "User Guide"
+weight = 9
+type = "docs"
+date = 2026-02-03
+url = "/en/docs/user-guide/"
++++
+
+This section contains the User Guide for Volcano.
+
+* [Ascend vNPU User Guide](/en/docs/user-guide/how_to_use_vnpu/)
+* [Capacity Plugin User Guide](/en/docs/user-guide/how_to_use_capacity_plugin/)
+* [Cooldown Protection Plugin User Guide](/en/docs/user-guide/how_to_use_cdp_plugin/)
+* [Extender User Guide](/en/docs/user-guide/how_to_use_extender/)
+* [GPU Number User Guide](/en/docs/user-guide/how_to_use_gpu_number/)
+* [GPU Sharing User Guide](/en/docs/user-guide/how_to_use_gpu_sharing/)
+* [How to Configure Scheduler](/en/docs/user-guide/how_to_configure_scheduler/)
+* [Volcano Job Policy User Guide](/en/docs/user-guide/how_to_use_job_policy/)
+* [Volcano Job Time to Live User Guide](/en/docs/user-guide/how_to_use_job_ttl/)
+* [Dynamic Resource Allocation (DRA) User Guide](/en/docs/user-guide/how_to_enable_dra/)
+* [How to Tune Volcano Performance in Large-Scale Scenarios](/en/docs/user-guide/how_to_tune_volcano_performance/)
+* [How to configure priorityclass for job](/en/docs/user-guide/how_to_configure_priorityclass_for_job/)
+* [MPI Plugin User Guide](/en/docs/user-guide/how_to_use_mpi_plugin/)
+* [NUMA Aware User Guide](/en/docs/user-guide/how_to_use_numa_aware/)
+* [Network Topology Aware Scheduling User Guide](/en/docs/user-guide/how_to_use_network_topology_aware_scheduling/)
+* [Nodegroup Plugin User Guide](/en/docs/user-guide/how_to_use_nodegroup_plugin/)
+* [Pytorch Plugin User Guide](/en/docs/user-guide/how_to_use_pytorch_plugin/)
+* [Ray Plugin User Guide](/en/docs/user-guide/how_to_use_ray_plugin/)
+* [Resource Strategy Fit Plugin User Guide](/en/docs/user-guide/how_to_use_resource_strategy_fit_plugin/)
+* [Task Topology Plugin User Guide](/en/docs/user-guide/how_to_use_task_topology_plugin/)
+* [HyperNode Auto Discovery User Guide](/en/docs/user-guide/how_to_use_hypernode_auto_discovery/)
+* [Volcano Job Plugin -- Env User Guide](/en/docs/user-guide/how_to_use_env_plugin/)
+* [Volcano Job Plugin -- SSH User Guide](/en/docs/user-guide/how_to_use_ssh_plugin/)
+* [Volcano Job Plugin -- SVC User Guide](/en/docs/user-guide/how_to_use_svc_plugin/)
+* [Volcano vGPU User Guide](/en/docs/user-guide/how_to_use_volcano_vgpu/)

content/en/docs/user_guide_how_to_configure_priorityclass_for_job.md

@@ -0,0 +1,66 @@
++++
+title = "How to configure priorityclass for job"
+date = 2026-02-03
+type = "docs"
+weight = 50
+url = "/en/docs/user-guide/how_to_configure_priorityclass_for_job/"
+[menu.docs]
+  parent = "user-guide"
++++
+
+
+## Background
+When a user creates a job, if there is no `PriorityClassName` specified in the template of the task, the task will use the `PriorityClassName` specified by the job. The user can specify `PriorityClassName` in each task's template to override the configuration of job, so that priority can be configured separately for each task.
+
+## Key Points
+- If the task does not specify `PriorityClassName` but the job does, the task will use the job's PriorityClass, and the `PreemptionPolicy` and priority value will also be the same as the job. 
+- When user needs to allow task in job to preempt other tasks if the resources are insufficient, a separate `PriorityClassName` must be set in the task's template, and **it is important to note that if there are multiple tasks that need to be set to different priorities, then user need to set the `PriorityClassName` for all of them**, otherwise the task that does not specify `PriorityClassName` will use the PriorityClass of the job it belongs to.
+
+## Example
+```yaml
+apiVersion: scheduling.k8s.io/v1
+kind: PriorityClass
+metadata:
+  name: job-priority
+value: 1
+preemptionPolicy: Never
+---
+apiVersion: scheduling.k8s.io/v1
+kind: PriorityClass
+metadata:
+  name: task-priority
+value: 10
+---
+apiVersion: batch.volcano.sh/v1alpha1
+kind: Job
+metadata:
+  name: job
+spec:
+  schedulerName: volcano
+  priorityClassName: job-priority
+  minAvailable: 1
+  tasks:
+    - replicas: 1
+      name: preempt-task
+      template:
+        spec:
+          priorityClassName: task-priority # The priorityclass is specified individually for this task
+          containers:
+            - image: alpine
+              command: ["/bin/sh", "-c", "sleep 1000"]
+              name: preempt
+              resources:
+                requests:
+                  cpu: 1
+    - replicas: 1
+      name: non-preempt-task # This task does not specify PriorityClassName, so it will use the "job-priority" priorityclass specified by job
+      template:
+        spec:
+          containers:
+            - image: alpine
+              command: ["/bin/sh", "-c", "sleep 1000"]
+              name: non-preempt
+              resources:
+                requests:
+                  cpu: 1
+```