Replies: 1 comment
-
Unfortunately, folder-based versioning is currently not supported. However, technically* it will be supported with the updated section navigation — available soon! See also the example below. *Technically it will work, but I'd like to make things a bit simpler and easier, update the UX — and support both folder-based and subdomain-based versioning. Will be part of the then next release Then, put your versioned documentation directly under content
├───docs
│ ├───guides
│ └───reference
├───main
│ ├───guides
│ └───reference
└───v1-12
├───guides
└───reference Customize URL's in [permalinks]
[permalinks.page]
main = "/docs/:sections/:slug/"
v1-12 = "/docs/v1.12/:sections[1:]/:slug/"
[permalinks.section]
main = "/docs/:sections/"
v1-12 = "/docs/v1.12/:sections[1:]/" Older version: Latest version: Latest development version |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I need assistance with enabling versioning on my GitHub documentation. I've managed to activate it by setting docsVersioning = true in the params.toml file.
However, when navigating to the documentation at docs/2.0/, the correct version is displayed, but the left-side menu still shows all versions (1.0, 2.0, etc.). How can I configure it to display only the content relevant to the current version based on the URL?
Having all versions listed in the side menu is confusing for users and I'd like to streamline it to only show the content corresponding to the version being viewed.
Beta Was this translation helpful? Give feedback.
All reactions