Also, you could implement versioning on your own using some shell scripts. You could build separate branches or tags of your git repository into separate folders and include a dropdown for version selection within the template. You could generate a Jinja template file which exports all generated versions as a macro. I used this technique to implement localization within Material, see:

mkdocs-material/material/partials/language/en.html

Lines 1 to 23 in e5069bb

    
           {% macro t(key) %}{{ { 
        
             "language": "en", 
        
             "direction": "ltr", 
        
             "clipboard.copy": "Copy to clipboard", 
        
             "clipboard.copied": "Copied to clipboard", 
        
             "edit.link.title": "Edit this page", 
        
             "footer.previous": "Previous", 
        
             "footer.next": "Next", 
        
             "meta.comments": "Comments", 
        
             "meta.source": "Source", 
        
             "search.language": "en", 
        
             "search.pipeline.stopwords": true, 
        
             "search.pipeline.trimmer": true, 
        
             "search.placeholder": "Search", 
        
             "search.result.placeholder": "Type to start searching", 
        
             "search.result.none": "No matching documents", 
        
             "search.result.one": "1 matching document", 
        
             "search.result.other": "# matching documents", 
        
             "search.tokenizer": "[\s\-]+", 
        
             "skip.link.title": "Skip to content", 
        
             "source.link.title": "Go to repository", 
        
             "toc.title": "Table of contents" 
        
           }[key] }}{% endmacro %}

Within your macro you could export a list and then import the generated Jinja template and iterate that list. Importing works like this:

mkdocs-material/material/partials/language.html

Line 2 in e5069bb

{% import "partials/language/en.html" as fallback %}

The fallback variable within this example can then be used as a variable within your template which you can iterate and generate a dropdown with the generated versions from. I hope that's helpful to you.

	{% macro t(key) %}{{ {
	"language": "en",
	"direction": "ltr",
	"clipboard.copy": "Copy to clipboard",
	"clipboard.copied": "Copied to clipboard",
	"edit.link.title": "Edit this page",
	"footer.previous": "Previous",
	"footer.next": "Next",
	"meta.comments": "Comments",
	"meta.source": "Source",
	"search.language": "en",
	"search.pipeline.stopwords": true,
	"search.pipeline.trimmer": true,
	"search.placeholder": "Search",
	"search.result.placeholder": "Type to start searching",
	"search.result.none": "No matching documents",
	"search.result.one": "1 matching document",
	"search.result.other": "# matching documents",
	"search.tokenizer": "[\s\-]+",
	"skip.link.title": "Skip to content",
	"source.link.title": "Go to repository",
	"toc.title": "Table of contents"
	}[key] }}{% endmacro %}

Manage multiple versions of documentation #770

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions