Deployment Workflow
Push to GitHub and your docs deploy automatically -- the workflow from local edits to a live site in minutes.
Jamdesk handles deployment automatically. Push to your connected GitHub branch and your docs go live within minutes.
CLI Deploy
You can also deploy directly from the terminal without pushing to GitHub. This is useful for quick iterations, testing changes, or projects not connected to a repo.
jamdesk login # First time only
jamdesk deployThe CLI packages your files, uploads them, and shows build progress live. Use --detach to queue the build and exit immediately.
The Workflow
Edit your MDX files and preview with jamdesk dev.
Commit and push to your connected branch:
git add .
git commit -m "Update authentication docs"
git pushJamdesk detects your push, builds your docs, and deploys to the CDN. Most sites build in 30-90 seconds.
Deployment Status
Check status in the dashboard under Deployments:
| Status | Meaning |
|---|---|
| Building | Build in progress |
| Deployed | Live at your domain |
| Failed | Build error - check logs |
| Queued | Waiting for previous build |
Manual Rebuild
Trigger a rebuild without pushing:
- Go to Settings in your project
- Click Rebuild
Use this when updating environment variables or fixing stuck builds.
Build Logs
When builds fail, check Deployments → click a deployment → view logs. Common issues:
- Invalid MDX syntax
- Missing images
- Broken internal links
- Configuration errors
Rollbacks
Revert to a previous version:
- Go to Deployments
- Find the deployment to restore
- Click Rollback
The previous version goes live immediately.