Documentation: Versioning the website

[feliblo]

Hi I'm seeing the following on the hextra website:

I would like to set this up for my own Hextra instance, but can't find anything when searching the docs for version. Is there a guide on how to set this up?

Thanks in advance!

[imfing]

Thanks for the question. Yes, this is possible with Hextra.

The Versions item in the screenshot is a normal nested menu.main dropdown, and each version is a separately built site deployed under paths like /versions/v0.10/.

public/
├── index.html
├── docs/
├── blog/
├── showcase/
├── assets/
├── ... (all files for the main/current docs site)
└── versions/
    ├── latest/
    │   ├── index.html
    │   ├── docs/
    │   ├── blog/
    │   └── ... (versioned site files)
    ├── v0.10/
    │   ├── index.html
    │   ├── docs/
    │   ├── blog/
    │   └── ... (versioned site files)
    └── v0.9/
        ├── index.html
        ├── docs/
        ├── blog/
        └── ... (versioned site files)

In this repo, that is handled in build.sh (build different refs/tags into public/versions/*) plus links in docs/hugo.yaml.

So it works today, but it is not an automatic built-in versioning feature.

[feliblo]

I will try to implement it using the description you gave. However since hextra seems to be turning into the most polished hugo for user focussed technical documentation, I would kind of expect it in the future, kind of a simple 'version tracking' and/or 'version_menu'. And incorporate it as a hook of some sort when bumping versions/tags.

Thanks for your work!