Docusaurus docs on Vercel – best setup?

Help
1

Hi,

we’re planning to host our product documentation on Vercel using Docusaurus.

Current state:

  • Docs are currently in Document360
  • Goal is a stable, production-grade docs site on Vercel

What we need help with:

  1. Recommended Vercel setup for Docusaurus

    • Build command
    • Output directory
    • Node/Yarn versions
    • Any Docusaurus-specific Vercel considerations

  2. Hosting Docusaurus at an existing subpath (/docs/)

    • Best way to serve Docusaurus from example.com/docs/ on Vercel
    • Whether this should be handled via:
      • Vercel project configuration
      • Reverse proxy / CDN routing
      • Framework-level baseUrl configuration

  3. Preview deployments

    • Best practices for using Vercel preview deployments for internal review before go-live
5

Hi @catherinep, welcome to the Vercel Community!

  1. We’ve this How to Deploy a Docusaurus Site with Vercel guide in our knowledge base that will be helpful.
  2. If your marketing side is hosted on Vercel, you can use the rewrites configuration in your vercel.json file to achieve this.
  3. You can use Vercel preview deployments without any additional set up. It should work automatically for PRs.
6

Thanks for the guidance and the link — this helps.

One clarification on our setup: our main marketing site is not hosted on Vercel. We are planning to host only the documentation on Vercel.

We’ve already created a local Docusaurus setup and will likely push it to GitHub as the next step before importing it into Vercel.

Since we need to retain the existing example.com/docs/ path, our understanding is that this would be handled via our existing reverse proxy, routing /docs/* → the Vercel Docusaurus deployment

Please suggest.