Missing VitePress documentation for stable version (v1.6.4 currently)

[vlcinsky]

Describe the bug

I have found VitePress and it seems to be great fit to our needs.

However:

• official site https://vitepress.dev offers only docs for v2.0.0-alpha.12 (the pop down shows only links to Changelog and Contributing)
• I was unable to find any site for stable version (currently v1.6.4)

I had to clone the repo and build the docs for v1.6.4 myself.

Is building docs for stable version of VitePress expected way, users access the docs?

Or are users already supposed to use the v2.0.0 alpha version?

Reproduction

Try to find VitePress documentation for latest stable version (currently v1.6.4)

The only one published is for v2.0.0-alpha.12

Expected behavior

Find somewhere:

• on a public URL
• or at least as downloadable artefact
  documentation for v1.6.4 (or other latest stable version).

System Info

not relevant

Additional context

The Validation check for this issue is advising me to use "the latest VitePress version" leading to v2.0.0-alpha.12

Validations

• Check if you're on the latest VitePress version.
• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

New users can start using v2-alpha. Some new features are there but most of the documentation still applies to v1 too. And there are no major breaking changes yet.

I think this is the latest available v1 deploy - https://679090956d67d00008489551--vitepress-docs.netlify.app/

[vlcinsky]

Thanks @brc-dd for the link to the v1.6.1 docs! It helps.

Your advice about new users starting with v2-alpha is helpful. It would be great to find such information in project README.md, along with:

• Which features are stable vs. experimental in v2-alpha
• A link to v1 documentation for users who prefer the stable release

The "alpha" designation typically signals to developers that breaking changes are expected. For beginners (as me), and for teams with strict stability requirements, having clear guidance about which version to choose—and easy access to stable version docs—would be valuable.

Would the team consider either:

1. Making the v1 docs more discoverable (perhaps linked from the main site)
2. Adding a version selector to vitepress.dev
3. Updating the README with clearer version recommendations?

[vlcinsky]

Taking into account, VitePress allows a switch for multiple versions, why not to add the latest stable docs version into new alpha one, especially when the API is supposed to be so similar.

[brc-dd]

VitePress allows a switch for multiple versions

Ah, versioning is not implemented yet. If you're referring to the version in navbar, then that's just a menu dropdown. I think I can create a deploy for v1 branch and link it from that navbar item.

[vlcinsky]

@brc-dd it was really quick. Great.