Skip to content

Fix versioning in mkdocs #60

@alexmerlin

Description

@alexmerlin

Bug Report

Replacing v1, v2 etc versioning notation does build without issues but the deployed docs thinks that the current and only version is not the most recent version but an an older version.
Also, TOC navigation is broken.

Image

In conclusion, we can keep the structure in docs/ but we need to keep using v1, v2 etc versioning notation.

Q A
Version(s) 1.0.14

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions