# Versioning > Customize navigation and banners for multiple versions of your docs. --- LLMS index: [llms.txt](/llms.txt) --- Depending on your project's releases and versioning, you may want to let your users access previous versions of your documentation. How you deploy the previous versions is up to you. This page describes the Docsy features that you can use to provide navigation between the various versions of your docs and to display an information banner on the archived sites. ## Adding a version drop-down menu If you add some `[params.versions]` in `hugo.toml`/`hugo.yaml`/`hugo.json`, the Docsy theme adds a version selector drop down to the navbar. You specify a URL and a name for each version you would like to add to the menu, as in the following example:

# Add your release versions here
[[params.versions]]
  version = "master"
  url = "https://master.kubeflow.org"

[[params.versions]]
  version = "v0.2"
  url = "https://v0-2.kubeflow.org"

[[params.versions]]
  version = "v0.3"
  url = "https://v0-3.kubeflow.org"

params:
  versions:
    - version: master
      url: 'https://master.kubeflow.org'
    - version: v0.2
      url: 'https://v0-2.kubeflow.org'
    - version: v0.3
      url: 'https://v0-3.kubeflow.org'

{
  "params": {
    "versions": [
      {
        "version": "master",
        "url": "https://master.kubeflow.org"
      },
      {
        "version": "v0.2",
        "url": "https://v0-2.kubeflow.org"
      },
      {
        "version": "v0.3",
        "url": "https://v0-3.kubeflow.org"
      }
    ]
  }
}

Remember to add your current version so that users can navigate back! The default title for the version drop-down menu is **Releases**. To change the title, change the site parameter `version_menu` in `hugo.toml`/`hugo.yaml`/`hugo.json`:

[params]
version_menu = "Releases"

params:
  version_menu: Releases

{
  "params": {
    "version_menu": "Releases"
  }
}

If you set the `version_menu_pagelinks` parameter to `true`, then links in the version drop-down menu point to the current page in the other version, instead of the main page. This can be useful if the document doesn't change much between the different versions. Note that if the current page doesn't exist in the other version, the link will be broken. You can also configure individual menu entries: - Use `name` instead of `version` when the menu label is not a version number. - Set `name` to `---` to add a menu separator. - Omit `url` to render a disabled text item, such as a group heading. - Set `kind` to add a kind-specific class for styling. For details, see [Navigation and menus][]. - Set `pagelinks: false` on an entry to link to that version's main URL even when the global `version_menu_pagelinks` parameter is `true`. For example: ```yaml params: version_menu: v1.2 version_menu_pagelinks: true versions: - name: '**Versions**' - version: v1.3-dev kind: next url: https://next.example.com - version: v1.2 kind: latest url: https://docs.example.com - name: --- - name: Preview variant kind: home pagelinks: false url: https://preview.example.com ``` To learn more about Docsy menus, see [Navigation and menus][]. [Navigation and menus]: /docs/content/navigation/#version-menu ## Displaying a banner on archived doc sites If you create archived snapshots for older versions of your docs, you can add a note at the top of every page in the archived docs to let readers know that they’re seeing an unmaintained snapshot and give them a link to the latest version. For example, see the archived docs for [Kubeflow v0.6](https://v0-6.kubeflow.org/docs/):

A text box explaining that this is an unmaintained snapshot of the docs. — Figure 1. The banner on the archived docs for Kubeflow v0.6

To add the banner to your doc site, make the following changes in your `hugo.toml`/`hugo.yaml`/`hugo.json` file: 1. Set the site parameter `archived_version` to `true`:

[params]
archived_version = true

params:
  archived_version: true

{
  "params": {
    "archived_version": true
  }
}

1. Set the site parameter `version` to the version of the archived doc set. For example, if the archived docs are for version 0.1:

[params]
version = "0.1"

params:
  version: 0.1

{
  "params": {
    "version": "0.1"
  }
}

1. Make sure that site parameter `url_latest_version` contains the URL of the website that you want to point readers to. In most cases, this should be the URL of the latest version of your docs:

[params]
url_latest_version = "https://your-latest-doc-site.com"

params:
  url_latest_version: https://your-latest-doc-site.com

{
  "params": {
    "url_latest_version": "https://your-latest-doc-site.com"
  }
}