# Deploy guides

Step-by-step guides for putting a static site live on thin.host, one per framework. Each covers the build command, the folder to deploy, the base-path setting for the `/s/<slug>/` preview URL, a prompt for your agent (Claude Code, Cursor, ChatGPT and other MCP clients), the equivalent `curl` call, and the custom-domain step.

| Guide | Build | Deploy this folder |
|---|---|---|
| [Astro](https://thin.host/guides/deploy-astro) | `npm run build` | `dist/` |
| [Vite (React)](https://thin.host/guides/deploy-vite-react) | `npm run build` | `dist/` |
| [Vue](https://thin.host/guides/deploy-vue) | `npm run build` | `dist/` |
| [SvelteKit](https://thin.host/guides/deploy-sveltekit) | `npm run build` | `build/` |
| [Next.js (static export)](https://thin.host/guides/deploy-nextjs) | `npm run build` | `out/` |
| [Nuxt (generate)](https://thin.host/guides/deploy-nuxt) | `npx nuxt generate` | `.output/public/` |
| [Gatsby](https://thin.host/guides/deploy-gatsby) | `npm run build` | `public/` |
| [Hugo](https://thin.host/guides/deploy-hugo) | `hugo --cleanDestinationDir --minify` | `public/` |
| [Jekyll](https://thin.host/guides/deploy-jekyll) | `JEKYLL_ENV=production bundle exec jekyll build` | `_site/` |
| [Eleventy (11ty)](https://thin.host/guides/deploy-eleventy) | `npx @11ty/eleventy` | `_site/` |
| [MkDocs](https://thin.host/guides/deploy-mkdocs) | `mkdocs build` | `site/` |
| [VitePress](https://thin.host/guides/deploy-vitepress) | `npm run docs:build` | `docs/.vitepress/dist/` |
| [Docusaurus](https://thin.host/guides/deploy-docusaurus) | `npm run build` | `build/` |
| [Plain HTML](https://thin.host/guides/deploy-html) | none | the folder with `index.html` |
| [An HTML page from a Claude or ChatGPT chat](https://thin.host/guides/deploy-ai-chat-html) | none | the folder with `index.html` |

## The same three steps for every framework

1. **Build static files** with the base path set for where the site will be read: `/s/<slug>/` for the thin.host preview URL, `/` for a custom domain.
2. **Deploy the output folder**: ask your agent to publish it through the thin.host MCP server, or zip it and `POST` it to `/v1/websites/archive`.
3. **Map a domain** from the dashboard (CNAME to `cname.thin.host`, automatic TLS), then rebuild with base `/`.

New to the MCP server? Start with [Quickstart (MCP)](https://thin.host/docs/quickstart-mcp). Moving from another host? See [thin.host compared](https://thin.host/compare).

---
Canonical page: https://thin.host/guides