Add vercel.json to deploy docs/ as the static site root - #20
Conversation
What: tells Vercel to serve docs/ directly as the output directory - no build command, since the docs site is plain static HTML/CSS/JS with no build step.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request adds ChangesVercel documentation deployment
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Feature Merge Risk: ⚪ Minimal · up to The configuration can serve the existing documentation site without a build step; no concrete deployment defect is established. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
vercel.jsonat the repo root telling Vercel to servedocs/directly as the output directory.docs/index.html,styles.css,script.js, from PR Rewrite docs site UI: fix mobile overflow, polish visual design #19) is plain static HTML/CSS/JS with no build step, so Vercel just copies the directory as-is.Test plan
vercel.jsonis a static output-directory config only - nothing to run locally to verify beyond reviewing the fileSummary by CodeRabbit
docsdirectory.