Need live agent support: Migrating docs to Docusaurus on Vercel while retaining /docs path

Help
1

Hi Vercel team and community,

We’re looking for support guidance for migrating our documentation to Docusaurus hosted on Vercel.

Context:

  • Our main website is not hosted on Vercel
  • Documentation currently lives at example.com/docs/
  • Docs are currently hosted on Document360
  • We want to host only the documentation on Vercel

Current status:

  • Local Docusaurus setup is already created
  • Next step would likely be pushing the repo to GitHub and importing it into Vercel

Key constraints:

  • We need to retain the existing /docs/ path
  • Our IT/security team operates under strict DNS and CDN controls

What we need help with:

  1. Recommended Vercel setup for Docusaurus (build command, output directory, Node/Yarn versions)
  2. Best practice for hosting Docusaurus on Vercel when the main site is external
  3. Confirmation that routing /docs/* → Vercel via an existing reverse proxy/CDN is the correct approach
  4. Any Vercel-specific considerations when Vercel sits behind an enterprise proxy/CDN
  5. Using preview deployments for internal review before go-live

I have gone through this - https://vercel.com/kb/guide/deploying-docusaurus-with-vercel

We’re posting here because we’re currently on the free plan and haven’t been able to connect with the sales team, but we’d appreciate technical support guidance from Vercel staff.

Thanks in advance for any direction or examples from similar setups.

5

Hey, @catherinep! Sounds like an exciting migration.

This might be a good time to get in touch with our solution partners to help you out :slight_smile: