Documentation about versioning across branches rather than a single directory

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Description

I have noticed that docusaurus lacks documentation about versioning across different branches rather than a single branch with a versioned directory, even if it is just a note about not being supported.

---

I wanted to set-up versioning for my project which uses separate branches for older versions (like master for current version, old/vX for older versions) and i have read that docusaurus supports versioning across branches, but i cannot find any documentation (even outside of the official documentation) regarding setting this up. The only vaguely similar things i found are basically setup a reverse proxy or depend on immutability from your provider, which is not really great for github pages or other static-only providers.

Self-service

• I’d be willing to address this documentation request myself.

[hasezoey]

You can have subpaths on a single GHP deployment, and it’s also outside the scope of Docusaurus (only baseUrl is part of the Docusaurus scope.

Taking the 3 distinct framework examples, you can have Jekyll on /v1, MkDocs on /v2, and Docusaurus on / or /v3.

Static deployments are just static files, you can just merge 3 static folders into one if you want, and push all the files to the gh-pages branch of your repo. That’s a complex setup and it’s your responsibility to figure out details on how to assemble just deployment. That’s DevOps, not Docusaurus.

thanks for the feedback, i just wanted to ask if there would be any problems with doing a nested (which it would be) docusaurus deployment to a sub-folder, while still having the main docusaurus up on the root in github-pages

[slorber]

np 👍

No problem, you just need to build the 2 docusaurus sites (one with baseUrl: '/' and one with baseUrl: '/v1') and merge the 2 static outputs as a single static site. Replace Docusaurus by any other SSG and the answer remains true: that’s not specific to Docusaurus but is just how static files and folders work 😄

The only thing that matters is that you have both ./index.html and ./v1/index.html in your deployment.