Deploy maintained historical versions of the Chinese documentation

[dogledogle]

Documentation is

• Missing
• Outdated
• Confusing
• Not sure?

Explain in Detail

Hi @bluwy , this is a follow-up to #21295.

I am a new maintainer of the Chinese documentation, and we would like to support and continue maintaining historical versions of the Chinese docs.

In the previous discussion, you mentioned that the Vite team could revisit historical deployments when a translation repository was willing to maintain the corresponding version branches. We have now prepared and are maintaining the following branches in vitejs/docs-cn:

• stable-5.x
• stable-6.x
• stable-7.x

The repository is ready on the translation-maintenance side. Could the Vite team please help us configure deployments for these historical branches?

Your Suggestion for Changes

Could we please deploy the maintained branches using the following mapping?

• stable-5.x → https://v5.cn.vite.dev
• stable-6.x → https://v6.cn.vite.dev
• stable-7.x → https://v7.cn.vite.dev

We would also appreciate it if each site could be automatically rebuilt and redeployed whenever commits are pushed to its corresponding branch. This would allow us to continue correcting and updating the historical documentation without requiring manual deployment coordination for every change.

We understand that maintaining historical documentation can introduce additional maintenance overhead. On the Chinese documentation side, we are prepared to take responsibility for the ongoing translation and content maintenance of these branches.

Please let us know if any repository configuration or workflow changes are required from our side. I would be happy to help with them.

Thank you for considering this request.

Reproduction

No response

Steps to reproduce

No response

[bluwy]

Awesome! This seems good to me. I don't have full permissions to set up the DNS on Cloudflare side, will need @sapphi-red's help to set this up.

Are you also on the Vite discord server? Let us know if you're there and we can add you the docs role so you can discuss and ping us there directly in the future.

[dogledogle]

Awesome! This seems good to me. I don't have full permissions to set up the DNS on Cloudflare side, will need @sapphi-red's help to set this up.

Are you also on the Vite discord server? Let us know if you're there and we can add you the docs role so you can discuss and ping us there directly in the future.

Thank you for your support and for reaching out to @sapphi-red to help with the Cloudflare DNS setup. I really appreciate your help in moving this forward.

I have just joined the Vite Land Discord server. My Discord username is dogledogle. I would be happy to receive the docs role and discuss documentation-related topics with the team there in the future.

Thanks again!

[zhouzhiouhub]

@bluwy @sapphi-red Since the DNS setup might take some time, I'd like to help by drafting a short DEPLOYMENT.md in the docs-cn repo. It would document:

• The branch-to-domain mapping (stable-5.x → v5.cn.vite.dev, etc.)
• The manual steps to trigger a rebuild after a push
• Any environment variables or Cloudflare settings that future maintainers need to be aware of

This way, once the DNS is ready, the deployment process is fully captured for everyone. Would that be helpful? If yes, I'll open a PR against the docs-cn repo referencing this issue.

[zhouzhiouhub]

@bluwy @sapphi-red I've opened a PR with the deployment guide:
vitejs/docs-cn#1749

Please review when you have time. Also happy to help with the GitHub Actions workflow for automated deployment later.

[LeonxLJX]

I'd like to take this one.

Reading the issue, this looks like a documentation-clarity gap rather than a code defect: the current page doesn't give readers enough to self-diagnose, which is why it surfaces here as an issue instead of being answered by the docs.

My plan: locate the relevant section, confirm the described behavior against the current source (so the docs match what the code actually does today, not what it did when the page was written), then tighten the wording and add the missing piece. I'll also scan neighboring pages for the same inconsistency, otherwise the fix just relocates the confusion.

One thing I'd like to confirm before writing: would you prefer a minimal correction scoped to this page, or should I also cross-link it from the related guides if the same gap shows up there?

(claiming via @LeonxLJX)