What it is:
- A tool for linking multiple versions of your project's Sphinx documentation, without the need for special services such as readthedocs.org.
- Useful if you build and host your documentation as a static site.
How it works:
versjonworks by injecting some basic HTML in to the generated documentation.
Install the
versjontool usingpip:python -m pip install versjon
Build all the different versions of your documentation into a common directory. For example generating all the docs in the
sitedirectory:git checkout 2.0.0 sphinx-build... -D version=2.0.0 ... site/build_2.0.0 ... git checkout 5.1.1 sphinx-build... -D version=5.1.1 ... site/build_5.1.1versjonwill use whateverversionis specified in the Sphinx configuration: https://www.sphinx-doc.org/en/master/usage/configuration.html If you have the specified theversionnumber inconf.pyyou can omit the-D versionoption to Sphinx build.- Run
versjonin the common directory - and you are done.
As default versjon will generate an index.html file with a redirect to the latest stable version, or if no semver version exists the first branch, presumably the master. You can disable this behavior with --no-index option.
As default versjon will generate a folder in the documentation root called stable. This folder will contain an index.html with a redirect to the latest stable version. You can disable this behavior with --no-stable-index option.
versjon ships with a couple of built-in templates, that get injected in the generated HTML:
head.html: This template gets injected into the<head>tag of the generated HTML pages. In this template you have access to the following variables:general,build,page.header.html: This template is inject at the beginning of the<body>tag. In this template you have access to the following variables:general,build,page.footer.html: This template is inject at the end of the<body>tag. In this template you have access to the following variables:general,build,page.index.html: This template is use to generate anindex.htmlin therootfolder. In this template you have access to the following variables:general,page.stable_index.html: This template is use to generate anindex.htmlin thestablefolder. In this template you have access to the following variables:general,page.
You can provide you own template for generating the version selector etc.
The easiest way is probably to copy one of the default HTML templates, e.g., src/templates/footer.html one and adapt it.
If you want to "inject" a custom footer. Create a file called footer.html and put it somewhere in your project, e.g., mydocs/footer.html now invoke versjon with the --user_templates argument, e.g.,:
./versjon --user_templates=mydocsverjson will prioritize finding templates in the users path first. If none is found it will fallback to the built-in.
If you want to disable a built-in template, simply create an empty file with the same name as the template you want to disable e.g. header.html if the template is empty no content will be injected.
In the templates you can access the information gathered by versjon. Based on this you can generate the needed HTML.
The following lists the various variables.
semver: A list of version dicts with a name which is a valid sematic version numbers, and a list of available files in this version.other: A list of version dicts with a name which non-semantic version numbers, and a list of available files in this version. Typically theotherlist will contain branches.stable: If we have any semantic version releases thestableversion will be the newest release in thesemverlist.docs_path: Dictionary mapping versions to the build folder for a version relative to the documentation root.
current: The current version nameis_semver: True if the current version follows semantic versioning
page_root: Relative path to the documentation root from a given HTML page. Concatenating thepage_rootwith a path indocs_pathwill give a valid relative link from one HTML page to the root folder of specific version.