You can use the version script to create a new documentation version based on the latest content in the
docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the
docs directory changes moving forward.
Think about it before starting to version your documentation - it can become difficult for contributors to help improve it!
Most of the time, you don't need versioning as it will just increase your build time, and introduce complexity to your codebase. Versioning is best suited for websites with high-traffic and rapid changes to documentation between versions. If your documentation rarely changes, don't add versioning to your documentation.
To better understand how versioning works and see if it suits your needs, you can read on below.
The table below explains how a versioned file maps to its version and the generated URL.
- First, make sure your content in the
docsdirectory is ready to be frozen as a version. A version always should be based from master.
- Enter a new version number.
When tagging a new version, the document versioning mechanism will:
- Copy the full
docs/folder contents into a new
- Create a versioned sidebars file based from your current sidebar configuration (if it exists) - saved as
- Append the new version number to
- Place the new file into the corresponding version folder.
- Include the reference for the new file into the corresponding sidebar file, according to version number.
- Remember to include the
- Files will be linked to correct corresponding version.
- Relative paths work as well.
Each directory in
versioned_docs/ will represent a documentation version.
You can update multiple docs versions at the same time because each directory in
versioned_docs/ represents specific routes when published.
- Edit any file.
- Commit and push changes.
- It will be published to the version.
Example: When you change any file in
versioned_docs/version-2.6/, it will only affect the docs for version
You can delete/remove versions as well.
- Remove the version from
- Delete the versioned docs directory. Example:
- Delete the versioned sidebars file. Example:
The "current" version is the version name for the
There are different ways to manage versioning, but two very common patterns are:
- You release v1, and start immediately working on v2 (including its docs)
- You release v1, and will maintain it for some time before thinking about v2.
Docusaurus defaults work great for the first usecase.
For the 2nd usecase: if you release v1 and don't plan to work on v2 anytime soon, instead of versioning v1 and having to maintain the docs in 2 folders (
./versioned_docs/version-1.0.0), you may consider using the following configuration instead:
The docs in
./docs will be served at
/docs/1.0.0 instead of
1.0.0 will become the default version we link to in the navbar dropdown, and you will only need to maintain a single
See docs plugin configuration for more details.
For example, you are building a documentation for your npm package
foo and you are currently in version 1.0.0. You then release a patch version for a minor bug fix and it's now 1.0.1.
Should you cut a new documentation version 1.0.1? You probably shouldn't. 1.0.1 and 1.0.0 docs shouldn't differ according to semver because there are no new features!. Cutting a new version for it will only just create unnecessary duplicated files.
As a good rule of thumb, try to keep the number of your versions below 10. It is very likely that you will have a lot of obsolete versioned documentation that nobody even reads anymore. For example, Jest is currently in version
24.9, and only maintains several latest documentation version with the lowest being
22.X. Keep it small 😊
Don't use relative paths import within the docs. Because when we cut a version the paths no longer work (the nesting level is different, among other reasons). You can utilize the
@site alias provided by docusaurus, that points to the
website directory. Example:
You should decide if assets like images and files are per version or shared between versions
If your assets should be versioned, put them in the docs version, and use relative paths:
If your assets are global, put them in
/static and use absolute paths: